Hi I was wondering if some one here could help me. I am running BE CleanRom ICS on HBoot 1.58 running the latest stock kernal. The phone shows no issues from from clean install. However when I try to restore my apps (approx 400) from my titanium backup set, the phone will be stable until i try to reset it. If I try to reset the phone once my apps are restored...the phone will bootup fine and then mount the SD card. I have a 64 GB micro SD card. It takes a while for the apps to load in the backround since I have majority of the apps installed to the card. However after a few minutes as the phone tries to load all the apps from the card, it will always crash.
I have logically considered that something was obviously wrong with the backups of my apps. So I tried to download all my apps fresh via Google play store again. I then moved them all again manually to the sd card. However I still get the same problem if I reset the phone. If I reset, the phone will try to load the apps from the microsd card after booting up and then after a while crash!
Is there any way to find out what is causing the phone to crash? I have tried different microsd cards as well. I have tried my older 32gb microsd card but get the same problems. Also I should note that when I was running older gingerbread version of cleanrom, after a reboot I would always get an error saying the HTC sense has crashed and needed to reload. But all that required was an 'ok' and the phone would relaod HTC sense and not crash into reboot.
I am hypothesizing that HTC sense 3.6 is crashing on reboot every time as it tries to load apps from the SD card. But I do not know how to confirm this. I have tried other roms including stock ics rom and meanrom 2.6 and have had the SAME issues with all these ICS roms. Is there any way to confirm that it is indeed HTC sense 3.6 that is causing the phone to crash while trying to load apps from the microsd card? And if so, is there any way to prevent or solve this problem?
At this point, I can NEVER reset my phone. If I do, I have to do a complete factory reset and then restore from my titanium backup to get my phone to previous state. This works fine until something FUBARS and my phone resets for whatever reason. Sometime it lasts for weeks without resetting....sometimes it happens numerous time a day. But everytime it resets I have to do a factory date wipe and then restore from my titanium backup and its a total pain in arse....
I would appreciate if anyone here could comment or offer any suggestions...
400 apps!!!!!!!!!!
That seems like an awful lot. Maybe having so many is causing the issue. I suggest maybe only loading the minimum you NEED as a test to see if it that's the issue.
Well maybe I should have been more specific. I have actually about 250 APPS, but when you count system backup and setting etc in Titanium backup it makes the total amount of backup items over 400.
But still I never had sense crashing on gingerbread? Why does Sense 3.6 crash on ICS and why can't I load that many apps from the SD card without it constantly crashing while trying to load? Is there a way to delay sense from loading until the SD card is mounted and all the apps are loaded into the app drawer? It makes no sense to not be able to install as many apps as you want....
I agree with you about installing add many as you can stuff in there. I was suggesting limiting them temporarily as a test.
Also, I wouldn't restore system apps saved from different ROMs as that can cause instability. Especially if you restore the settings from a GB system app to an ICS ROM.
Imagika FTW... with Tapatalk 2
Hi thanks for your response. Yeah I did not restore any systems files from my old GB rom. I did a fresh install of all my apps and settings once I moved to ICS. I use my titanium backup files to restore to the same rom I made the backups from...
Also, I was messing around with autostarts to see if I could disable Sense from booting up, but that didnt work either. Basically it seems like if you have too many apps loaded to the sd card then the OS seems to fubar while trying to reload and causes reset boot. Its quite unnerving...
I'm going to mess around with some of the roms with sense removed to see if that solves the problem. Will report back to this thread to post back my results....
I think it is the 64GB card. My Amaze is doing the same thing and I found this thread via the search tool. I'm getting ready to try a format and start fresh. It started when I got the card, and pulling the card out for a few days I don't get the reboots.
So being a different phone, different ROM, and different apps, the only things in common are the same SDXC and reboots. If I find a better solution, I'll update you.
gfunkmagic said:
I would appreciate if anyone here could comment or offer any suggestions...
Click to expand...
Click to collapse
Not sure what your problem is but you might want to consider installing Link2SD, which allows you to move most of your apps to a second partition on the SD card. This also has the advantage of not installing the apps on a fresh install until you create the mount script for the parition containing the apps, and also allows you to keep your apps across fresh installations without having to restore them. Just relink them to the partition on the SD card and they will all be "restored" in less than a minute.
There's a little work involved in backing up your SD card, creating new paritions, and restoring the SD card contents to the first partition, but 4EXT recovery can handle the partitioning and it's pretty easy to save and restore the SD card contents from a PC.
ramjet73
St Veronus said:
I think it is the 64GB card. My Amaze is doing the same thing and I found this thread via the search tool. I'm getting ready to try a format and start fresh. It started when I got the card, and pulling the card out for a few days I don't get the reboots.
So being a different phone, different ROM, and different apps, the only things in common are the same SDXC and reboots. If I find a better solution, I'll update you.
Click to expand...
Click to collapse
Hi thanks for you response. I actually already tried reverting to my old 32 GB card when I started having these problems and kept getting the same reset issues, so I'm not sure if this is a sd card issue or a issue with ICS or Sense on my device. I did not have the reset problem while using GB rom running the 32 SD card.
I don't get the reboots either if I pull out the card but then I dont have access to most of my apps! Trying to mount and remount the card doesn't seem to help either and causes the device to reset...
ramjet73 said:
Not sure what your problem is but you might want to consider installing Link2SD, which allows you to move most of your apps to a second partition on the SD card. This also has the advantage of not installing the apps on a fresh install until you create the mount script for the parition containing the apps, and also allows you to keep your apps across fresh installations without having to restore them. Just relink them to the partition on the SD card and they will all be "restored" in less than a minute.
There's a little work involved in backing up your SD card, creating new paritions, and restoring the SD card contents to the first partition, but 4EXT recovery can handle the partitioning and it's pretty easy to save and restore the SD card contents from a PC.
ramjet73
Click to expand...
Click to collapse
Thanks ramjet for the suggestion! I will definitely try out Link2SD to see if that resolves the problem! You posts are like the bible around here and I appreciate you offering your help! :good: THANKS!
ramjet73 said:
Not sure what your problem is but you might want to consider installing Link2SD, which allows you to move most of your apps to a second partition on the SD card. This also has the advantage of not installing the apps on a fresh install until you create the mount script for the parition containing the apps, and also allows you to keep your apps across fresh installations without having to restore them. Just relink them to the partition on the SD card and they will all be "restored" in less than a minute.
There's a little work involved in backing up your SD card, creating new paritions, and restoring the SD card contents to the first partition, but 4EXT recovery can handle the partitioning and it's pretty easy to save and restore the SD card contents from a PC.
ramjet73
Click to expand...
Click to collapse
Hi ramjet, I was wondering if you could help with setting up Link2SD? I was able to setup a fat32 partition on my 64GB card but when try to start link2SD i keep getting the "Mount script cannot be created" error when I try to select the fat32 partition? I went through the link2sd tutorial but couldn't get it to recognize the fat32 partiion. The link2sd faq states you have to be s-off for HTC devices and I am already s-off running hboot 1.58. I created the partitions using 4ext from scratch removing all partitions and creating new ones.. Do you have any suggestions? thanks...
gfunkmagic said:
Hi ramjet, I was wondering if you could help with setting up Link2SD? I was able to setup a fat32 partition on my 64GB card but when try to start link2SD i keep getting the "Mount script cannot be created" error when I try to select the fat32 partition? I went through the link2sd tutorial but couldn't get it to recognize the fat32 partiion. The link2sd faq states you have to be s-off for HTC devices and I am already s-off running hboot 1.58. I created the partitions using 4ext from scratch removing all partitions and creating new ones.. Do you have any suggestions? thanks...
Click to expand...
Click to collapse
Link2SD will automatically use the second partition on the SD card as the one it mounts to store the app files and data. I've got mine setup as a 1GB ext4 partition, but a fat32 formatted partition should work as well.
When you choose "recreate mount script" from the "more" options of the primary menu, it will ask for the format of the second SD partition and you need to select "FAT32/FAT16". That should create a mount script in the /system/etc/init.d directory that will get run on the next boot, assuming your ROM runs init.d scripts correctly. Which ROM are you currently using?
ramjet73
Hi I'm running BE Cleanrom ICS. I created the partitions using this 4ext guide. The following is my partition info on the 64 GB sd card:
partition // fs // capacity // free
system // ext4 // 787 MB // 141 MB
data // ext3 // 1175 MB // 588 MB
cache // ext4 // 107 MB // 96 MB
sd-ext // ext4 // 4031 MB // 3898 MB
sdcard // fat32 // 56780 MB // 39056 MB
If I select "ext4" on startup of link2sd when it asks me to select the file system of you sd card's second partition, then the mount script is successfully created. Does this mean it is selecting the "sd-ext" partition as the second partition? if so then maybe I've been confused the whole time?? The only thing is that I wish it was possible to create larger partitions than just 4GB....
gfunkmagic said:
Hi I'm running BE Cleanrom ICS. I created the partitions using this 4ext guide. The following is my partition info on the 64 GB sd card:
partition // fs // capacity // free
system // ext4 // 787 MB // 141 MB
data // ext3 // 1175 MB // 588 MB
cache // ext4 // 107 MB // 96 MB
sd-ext // ext4 // 4031 MB // 3898 MB
sdcard // fat32 // 56780 MB // 39056 MB
If I select "ext4" on startup of link2sd when it asks me to select the file system of you sd card;s second partition, then the mount script is successfully created. Does this mean it is selecting the "sd-ext" partition as the second partition? if so then maybe I've been confused the whole time?? The only thing is that I wish it was possible to create larger partitions than just 4GB....
Click to expand...
Click to collapse
That guide has you format the second SD card parition as ext4 so you should be good to go.
Start Link2SD and go to menu/storage info. The "SD Card 2nd Part." will confirm that your app parition is mounted correctly and give you the usage stats. Mine is allocated as 1GB with 182 apps linked to that partition and I still have 7% free, so I think 4GB should be more than enough.
I think it is always mounted as sd-ext regardless of which format you used. If you go to /data/sdext2 with ES File Explorer or similar app you can see all the .apk files that have been linked as well as the data and dalvik-cache directories.
Don't forget to recreate your mount script (you should be prompted after installing Link2SD) and relink your apps when you do a fresh install of a ROM to get all the applications you have installed linked to the current ROM. You also should backup the "SDext" partition whenever you use 4EXT to create a nandroid backup since that partition will contain all your linked apps and data.
ramjet73
ramjet73 said:
That guide has you format the second SD card parition as ext4 so you should be good to go.
Start Link2SD and go to menu/storage info. The "SD Card 2nd Part." will confirm that your app parition is mounted correctly and give you the usage stats. Mine is allocated as 1GB with 182 apps linked to that partition and I still have 7% free, so I think 4GB should be more than enough.
I think it is always mounted as sd-ext regardless of which format you used. If you go to /data/sdext2 with ES File Explorer or similar app you can see all the .apk files that have been linked as well as the data and dalvik-cache directories.
Don't forget to recreate your mount script (you should be prompted after installing Link2SD) and relink your apps when you do a fresh install of a ROM to get all the applications you have installed linked to the current ROM. You also should backup the "SDext" partition whenever you use 4EXT to create a nandroid backup since that partition will contain all your linked apps and data.
ramjet73
Click to expand...
Click to collapse
Ramjet you are the man!:highfive:
Finally moved all my apps to the partition using link2Sd and no forced crashes after reset! Yaaaaaaaaaaaaaaaaaaaay!
Everything is good to go now and I don't have to worry about reinstalling or restoring my device if it crashes! I have questions though about backups? When backing up user apps via Titanium...I am assuming it is only backing up the symbolic links correct? Even though the apps have been moved to the 2nd partition on the card, I still see the apps listed as on the phone in settings. Should you still use Titanium to backup user apps or is that a waste of time because it will only backup the symbolic links? I still will use it to backup my system settings and user apps. The reason I ask is because I use Titanium to make remote backups of all my settings and apps. Is there anyway to continue to do this using link2sd?
Thanks again for all you help!
gfunkmagic said:
Everything is good to go now and I don't have to worry about reinstalling or restoring my device if it crashes! I have questions though about backups? When backing up user apps via Titanium...I am assuming it is only backing up the symbolic links correct? Even though the apps have been moved to the 2nd partition on the card, I still see the apps listed as on the phone in settings. Should you still use Titanium to backup user apps or is that a waste of time because it will only backup the symbolic links? I still will use it to backup my system settings and user apps. The reason I ask is because I use Titanium to make remote backups of all my settings and apps. Is there anyway to continue to do this using link2sd?
Thanks again for all you help!
Click to expand...
Click to collapse
Titanium Backup (TB) will backup and restore apps fine with Link2SD installed, and the apps and data in the TB directory on the SD card are the actual objects, not the symbolic links. I consider the apps maintained by Link2SD in the second partition of the SD card as my primary backup for user apps, but do periodically delete all TB backups and make a full TB backup of all apps and data (system and user) just so I have a complete backup. Of course, I still have my nandroid backups as well, but if I accidentally uninstall something from Link2SD it's easier to restore with TB.
I've read that restoring all user apps from TB at once doesn't work because the Link2SD autolink isn't activated by a TB restore and the internal storage will overflow, but that's not a concern for me since I keep all my user apps in the Link2SD partition and never have to restore them all from TB. I think this may have been changed in a recent version of TB and/or Link2SD because when I just uninstalled an app and restored it with TB it was autolinked by Link2SD.
Just keep in mind that some formatting options, such as "format all partitions except SD card" in 4EXT, will format the sd-ext partitions so it's always a good idea to include them in your nandroid backups just to make sure you have a recent copy of the Link2SD apps.
BTW, one of the main advantages of Link2SD is that since it uses a separate partition on the SD card, the apps it links are still available when the first (usually fat32) SD card partition is mounted as USB storage. That's why the app manager thinks they are still on internal storage instead of the SD card.
ramjet73
Related
Hey! I have a fast, dumb, question! What does each partition do? I wanna partition my new SD card through amon_ra 1.5.2 and it says swap size, ext2 and FAT32 size... what's what! and whats the recommended for an 8gb card class 4
swap is not needed necessarily, it is used to store stuff when ram is going low. fat32 is the part where your music, pictures etc are stored (the part that gets mounted on your pc when you want to copy files), and ext2 is the part where apps2sd stores the apps.
ext2 (or 3 or 4) and fat32 are the filesystems that are created on the partitions, that is why they are called this.
kendong2 said:
swap is not needed necessarily, it is used to store stuff when ram is going low. fat32 is the part where your music, pictures etc are stored (the part that gets mounted on your pc when you want to copy files), and ext2 is the part where apps2sd stores the apps.
ext2 (or 3 or 4) and fat32 are the filesystems that are created on the partitions, that is why they are called this.
Click to expand...
Click to collapse
i have 1028Ext2, 128swap and the rest is fat32! is that ok?
Shei77 said:
i have 1028Ext2, 128swap and the rest is fat32! is that ok?
Click to expand...
Click to collapse
not sure about the order, but basically yes. you don't need swap, and your ext is probably big enough for >3000 apps (read: too big), but as long as you are happy you can leave it that way.
kendong2 said:
not sure about the order, but basically yes. you don't need swap, and your ext is probably big enough for >3000 apps (read: too big), but as long as you are happy you can leave it that way.
Click to expand...
Click to collapse
really?Lol!
btw are apps supposed to take any "space"? In Modaco 2.9 i lost some internal space on all the apps i installed? is it supposed to take some memory from 100mbs of my htc hero internal memory?If yes, how to remove it, if not, omg modaco 2.9 was bad?
Also is having like 1000 apps making my phone slower? I dont actually have that many, i have 60 i think, if i remove some will it make it any faster?
Also, if i change my ext2 now to like 500mb will it delete any of my current apps or "break" anything?
apps take space from internal memory, search for "apps2sd not working", it is explained in these threads more than enough. you can move the dalvik-cache to the ext partition, then you won't loose any internal space. doesn't seem necessary, i have about 280 apps installed and still 16mb internal left. having the apps does not slow down the phone, only extends the time for first boot after flashing. apps only make the phone slower when they are running, which i control with autostarts.
if you change the ext size partition your apps will be deleted, as will be the rest of the contents of the sdcard. there ways to do it without deleting anything, but frankly, when you need to ask it would be too complicated. would be more effort than make a backup, copy the contents of your sdcard to pc, repartition, copy contents back and restore the backup. that's the way to go btw.
if you uninstalled some/a lot of apps you can regain a few mb by deleting dalvik-cache from recovery. first boot after that may take a while.
kendong2 said:
apps take space from internal memory, search for "apps2sd not working", it is explained in these threads more than enough. you can move the dalvik-cache to the ext partition, then you won't loose any internal space. doesn't seem necessary, i have about 280 apps installed and still 16mb internal left. having the apps does not slow down the phone, only extends the time for first boot after flashing. apps only make the phone slower when they are running, which i control with autostarts.
if you change the ext size partition your apps will be deleted, as will be the rest of the contents of the sdcard. there ways to do it without deleting anything, but frankly, when you need to ask it would be too complicated. would be more effort than make a backup, copy the contents of your sdcard to pc, repartition, copy contents back and restore the backup. that's the way to go btw.
if you uninstalled some/a lot of apps you can regain a few mb by deleting dalvik-cache from recovery. first boot after that may take a while.
Click to expand...
Click to collapse
so apps shouldnt take ANY internal memory? if they do i should move dalvik-cache from amon_ra or apps2sd?
autostarts btw?
how to remove dalvik-cache from uninstalled apps? aint it supposed to be auto-deleted when i uninstall apps?
Shei77 said:
so apps shouldnt take ANY internal memory? if they do i should move dalvik-cache from amon_ra or apps2sd?
autostarts btw?
how to remove dalvik-cache from uninstalled apps? aint it supposed to be auto-deleted when i uninstall apps?
Click to expand...
Click to collapse
they are supposed to take internal space, because they use some space from dalvik-cache. if you move the dalvik-cache to the ext partition of the sdcard then the space is not taken from the internal memory but from the sdcard, obviously...
check the market, with autostarts you can stop applications from being started automatically.
like i said, clear dalvik-cache in recovery image via the menu item and then wait a few minutes for the phone to reboot...
kendong2 said:
they are supposed to take internal space, because they use some space from dalvik-cache. if you move the dalvik-cache to the ext partition of the sdcard then the space is not taken from the internal memory but from the sdcard, obviously...
check the market, with autostarts you can stop applications from being started automatically.
like i said, clear dalvik-cache in recovery image via the menu item and then wait a few minutes for the phone to reboot...
Click to expand...
Click to collapse
may i ask, how can i move the dalvik-cache to my SD card? i actually want my apps to take NO memory AT ALL on my internal memory..
Hi,
I'm getting low on space message on my hero running VillainRom 6.1. Tried rebooting, still there. I've only tried to install one or 2 apps with the message there, so not sure if thats actually been affected.
settings-->sdcard & phone storage-->internal storage shows 14.83mb
quick system info shows:
sd card storage free 2.14gb
a2sd storage 249mb free (total 457mb)
system cache 129mb free
memory 37.35mb free
there doesn't seem to be any more processes running than usual - only around 3-4.
I do have quite a lot of apps, over 100, probably closer to 200, I havent counted.
btw thanks to everyone on this site, I'm new to flashing roms but having fun learning, and my phones definitely got a new lease of life.
use the apps2sd checker to make sure its working. If it is id say increase your partition from 512 to more
Just because the app is installed on the sd card (assuming its working properly) doesn't mean the davilk cache for the app has moved. unless you move this as well (which isn't really recommended) each time you install an app system memory will still go down a little.
Lennyuk said:
Just because the app is installed on the sd card (assuming its working properly) doesn't mean the davilk cache for the app has moved. unless you move this as well (which isn't really recommended) each time you install an app system memory will still go down a little.
Click to expand...
Click to collapse
http://4943922026776299669-a-180274...lcSrZUn2-7KkHiRo-ew0R2SEebAQ==&attredirects=0
u need this which is an update. copy this file into the root of the memory card and through the recovery image install it from "zip file from sdcard"
after that restart the phone and check your memory is should be 120mb
Indy_Hero said:
use the apps2sd checker to make sure its working. If it is id say increase your partition from 512 to more
Click to expand...
Click to collapse
thanks for the suggestion
a2sd check script says its working fine, also checked via adb shell.
This is what I then did to the partition size:
I copied SD card contents (both partitions) into ubuntu.
then I put SD back into phone and repartitioned using 1gb for ext2
then I copied back SD card contents from ubuntu.
I assumed this would work, but when I booted I was getting FC all the time. Bart backup sorted it out but I am still left wondering why this method of increasing partition size didnt work??
In any case quick system info shows a2sd has more space, but still got low space message.
qasi said:
...
u need this which is an update. copy this file into the root of the memory card and through the recovery image install it from "zip file from sdcard"
after that restart the phone and check your memory is should be 120mb
Click to expand...
Click to collapse
seems to have solved the problem!! thanks alot mate.
would you by any chance out of interest know why copying ext2 contents from sdcard as outlined above didnt work? - may have some future relevance if changing/upgrading roms.
Thanks again
neuro_99 said:
thanks for the suggestion
a2sd check script says its working fine, also checked via adb shell.
This is what I then did to the partition size:
I copied SD card contents (both partitions) into ubuntu.
then I put SD back into phone and repartitioned using 1gb for ext2
then I copied back SD card contents from ubuntu.
I assumed this would work, but when I booted I was getting FC all the time. Bart backup sorted it out but I am still left wondering why this method of increasing partition size didnt work??
In any case quick system info shows a2sd has more space, but still got low space message.
seems to have solved the problem!! thanks alot mate.
would you by any chance out of interest know why copying ext2 contents from sdcard as outlined above didnt work? - may have some future relevance if changing/upgrading roms.
Thanks again
Click to expand...
Click to collapse
this is because the ramon recovery image had been linked with ext2 with a 512mb partition and u selected 1gb. im not quite sure about that.
chnagin rom is quite simple beucase you have to is
1.backup using nandroid
2.make sure you wipe everything. (also battery and rotating settings)
3. Re partition your sdcard to hold 1 ext2 partition and last partition should be the rest in fat32
4. Flash the rom you want through "zip file from sd card"
5. Reboot.
im a newb so i dont have much knowledge but patching up problems that i had, so that i can help others.
it can be pain especailly rooting!!!
So thats how you would flash a rom, but what if you wanted to keep your a2sd apps? So you dont have to install them all over again in the new rom when you wiped everything.
I think I read somewhere that it should be possible to leave the contents of ext2 as it is, and that should carry forward to the next rom, but I havent been able to test it myself yet.
I installed the magnificent Cronos 0.0.9 ROM (Android 2.3 Gingerbread) in my HTC Hero, following dkelley's instructions on the Developer forum for that device. It works brilliantly, speed is superb, and it looks like battery life is going to be better than the Cyanogen 6.1 it replaced.
Everything works for me : Camera, compass, GPS (sort of), auto brightness.
But there is one unusual problem. I cannot find any other forum threads that refer to this. When I use menu->Settings->Applications->Manage Applications, I can move apps to or from the SD card. Except it doesn't work most of the time. I get this message: "Failed to move application. There is not enough storage left"
I have 24MB free on the phone and 2.4GB free on the SD card. So it should not have a problem when I try to move anything (all but 2 of my apps are under 7MB). I have seen a case of being successful with an app of 730K moving to SD. But when I remove that, and try again with a 410K app, it fails. 90% of apps I have tried have failed.
I was very successful with this in my previous ROM, so I know it's not read errors on the SD.
I did forget to delete the old apps dot directory on the SD card before the upgrade. I don't know if that can cause a problem.
As I am too shiny and new, I can't post on the developer forum. A good rule, if it keeps the noise level slightly lower.
So I thought I would post here & see if anyone knows of general fixes for app 2 SD problems of this kind. Maybe it's just that the ROM is too Beta & it's to be expected. That's what happens out at the ragged edge
If u don't have an ext partition on your sdcard then I'm afraid it won't work on Cronos GB 0.0.9 Beta because the apps moved to External are moved on the fat partition and they Force Close all the time anyway on this rom. Now ... app2sd works verry weird on this rom. If u have an ext partition on your sdcard and if u want your apps to be on that partition (and they wont FC on you) all you need to do is let them on Internal (move to phone) and not External (move to sdcard). The apps are installed/moved to the ext partition instead and not on the phone's actual memory (again... as I said weird but it works). If u want to be able to move the apps to sdcard .. I recomend you back-up your files from sdcard to your pc, go to recovery and make an ext partition and wipe it(just in case) and boot your phone and try installing your apps.I'm installing my apps automaticaly to the ext partition by choosing the Install Location to Internal from CM Extra->Application settings. Sorry I wrote alot and if I haven't made myself clear but I'm still at work (3rd shift) and I am tired.
Example: I have a 2gb sdcard... On it I have the ext partition of 240MB, the rest is the fat partition.If I leave my apps on Internal(move to phone), my Phone's Memory is 140/173MB and my ext partition 47.5/240MB .. If I move them to External(move to sd card), My Phone's Memory is 140/173 and my ext partition is about 230/240 MB because the apps are moved to the fat partition (with your errors) and they Force Close when launched on this rom.
You're right, I can see that in the release notes. I am surprised, it's a long time since I have used a ROM that supported ext partitions. Most of them seem to use the Google apps2SD method now.
Cyanogen has even stated that it is no longer officially supported by them.
So I guess it's just individual developers who still prefer the ext approach that still use it.
It's not too hard to do...
Thanks for the tip
You're welcome! Remember that your sdcard content will be deleted when you will partition your sdcard so make a backup if you need them. I find ext is better than normal because you can use the apps from your sdcard while you phone is connected to the computer (your PC mounts the fat partition and leaves the ext partition to be used as normal on the phone and I find that a good thing)
Sorted it out the hard way - repartitioned with FAT and lost all my apps. Installed them quickly enough with Applanet App Market.
Theshawty said:
Hello XDA. A few months ago I partitioned my 2GB SD-card to use with a custom made 2.1 ROM I used to have and I have not changed this partitioning ever since, I've been using it with MiniCM and it works alright.
My question is: Could I or could I not partition it back to FAT so I don't have any ext without problems? Or do I need to reinstall MiniCM if I installed it with an ext partition?
Click to expand...
Click to collapse
One thing you need to check is if you have chosen 'internal memory' as the place to download applications that you may have downloaded/installed after installing CM1.In that case,choose the 'move to phone' option so that you don't have any apps stored on your ext partition.As long as you have stored apps either in the phone or external which is the FAT partition,there will be no problem at all in getting rid of the partition.Personally,I have never liked any of these ext partitions because I think they slow down the apps stored on them!
...do press the thanks button if this helps...........
Please clearly state which ROM are you going to flash, and the current partition details, partition(s) and size, filesystem ;-)
what is the ext2/ext3 partitions being used for ? are they only for setup new roms or for use while running the device?
i havent noticed any change with or without ext3 partition beside the low space left on the 2gb memory card...
eladmagen said:
what is the ext2/ext3 partitions being used for ? are they only for setup new roms or for use while running the device?
i havent noticed any change with or without ext3 partition beside the low space left on the 2gb memory card...
Click to expand...
Click to collapse
ext partitions are required to install apps2sd or link2sd so that you can store downloaded applications there instead of clogging your phone memory.These are not required if your OS is Froyo and higher since there is a native apps2sd which helps you move applications to the main FAT portion off the sd card.
-----------press the thanks button whenever you find any post useful........
Above the hood
Well today I intended to answer voyager's problem which was stated in the interactive data2sd thread located here http://forum.xda-developers.com/showthread.php?p=23744977#
and then i think that after i have gathered so much information from the other parts of the world into this little post it would be a waste if it is pushed away by regular posts in the thread. so, i opened this thread here in the general forum so all people with similar confusion can read about it.
YES, there are SO MANY WORDS TO READ. but in order to use a2sd+ or data2sd+ you MUST read them all
you will never know how frustrated i was when i was encountering the bootloop problem for the ENTIRE month.
my report thread - http://forum.xda-developers.com/showthread.php?t=1239063
my help-seeking in the darktremor thread which was answered by famous developer temasek - http://forum.xda-developers.com/showthread.php?p=17232233
my target was originally voyager the person but now its to all of you, please ignore my incorrect pronouns, if there are any
OH FINALLY i luckily found the very useful reference that i have read before!! after reading these you will understand everything
tobydjones said:
Some phones, eg the Desire, don't have enough internal memory (NAND). A2SD and other 'init.d scripts' fool Android into storing various things on the SD card instead of internal memory to free up space. They can move either apps, the Dalvik cache (a pre-compiled copy of each app) and/or app data. And they can move them to either the 1st (only) partition of the SD card (formatted as FAT or FAT32) or a 2nd partition of the SD card (formatted as ext3 or ext4).
As there's so many different scripts doing different things, I had to make a table to sort it all out. Please let me know if I've made any mistakes, or if you can answer any of my questions in italics.
script ................ apps . Dalvik . data .. comment
---------------------------------------------------------------------------------------------------------------
A2SD pre Froyo ........ SD ... int .... int ... Made to move app data to SD {or was it already ext?}
Froyo A2SD/"move to SD" SD<1>. int<9> . int ... Built in
Gingerbread A2SD ...... SD.... int .... <6> ... Built in. As Froyo but a bit more space.
apps2sd app (on market) ....................... App to make Froyo/Gingerbread "move to SD" easier, not a script
Force2SD (on market) .. ....................... As apps2sd + move system apps>SD {does apps2sd also do this?}
A2SD/AS2D+ (or apps2SD) ext<8> in/ex<2> int ... Various implementations<7> some move Dalvik (manual/auto)
Darktremor A2SD/DT-A2SD ext .. in/ex... int ... Move Dalvik. Used to be auto, now command line (or use A2SDGUI)
MIUI_Au PC-A2SD ....... ext .. ext .... int ... Allows android to boot if SD Card broken/removed. With logs
Link2SD (on market) ... ext .. ext .... <6> ... Moves apps individually
Sibere DATA2SD ........ ext .. ext .... ext<3>. Moves whole /data folder to ext for more space <4><5>
DATA2EXT .............. ext .. ext .... ext ... {another implementation of DATA2SD? how does it differ?}
data2whatever/DATA2WE . ext .. ext .... ext ... Can use ext2-4 plus variety of unusual filesystems eg B(RT?)FS
Notes:
<1> The SD card is mounted very late in the boot up process, so background apps and widgets won't work. Also apps on SD aren't available when SD card is used as a disk ('mounted')
<2> Dalvik on SD/ext may wear out SD card a bit quicker {not a big issue compared with int memory wearing out?}
<3> Data on ext wears out SD card faster because of data writes {how much of an issue is this?}
<4> Data2SD on Sense ROMS - possible corruption during battery pull or forced reboot
<5> Data2SD on ASOP ROMS - corruption when turning off phone due to unclean dismount {or is this fixed now?}
<6> GB doesn't move all of data, but does move app libs (/data/data/<appname>/Lib)
<7> There's a lot of confusion what AS2D, AS2D+ and apps2sd refer to, and the distinction between them, as those names been used for many things, including an app on the market! The + appeared after Froyo was released and often means the Dalvik cache can be moved (not always automatically)
<8> Unlike moving apps to SD, you can move widgets to ext, and apps are available when SD card is used as a disk
<9> If Dalvik cache is on int, number of apps is still limited as pre-compiled copy of each app held in cache
Updated 01/10/11. Thanks to rootSU, fllash & rmcsilva for corrections and additions
Click to expand...
Click to collapse
neoKushan said:
Ok, so here's the deal, in a very longwinded way that should hopefully explain everything and answer ALL questions.
You have an SD card in your phone and, a bit like normal PC Hard Drives, you can "partition" them (split them into two or more sections of different filesystems). Normally, your SD card is just one big FAT32 partition, which is fine for storing your pics, messages, emails, etc.
Now, other then your Phone's SD card, your phone will have its own internal flash memory (or "NAND") storage. Tradditionally with Android, you could only install applications to this NAND storage, you cannot install them onto your SD card. So if you have an empty 32GB SD card, but only 5Mb of internal phone storage, you still wont be able to install many apps, if any at all.
This was done to protect the apps from things like piracy - it's not easy to access the location where apps are installed on your phone's internal storage (normally impossible without root), so you can't for example buy an app, copy it, refund it, then install it again.
Still, this is no good for those of us who like to install lots and lots of apps, legitimately, as we run out of internal storage very quickly.
So Google came up with a way to install apps to the SD card. A folder is created called something like .android_secure and this stores (I believe) encrypted versions of applications, but there's a few catches:
1) Apps aren't automatically stored here, you have to manually "move" them
2) Not all apps are capable of being moved, in fact most apps aren't, the developer needs to update their app and allow it. Some apps aren't and wont be updated and some developers may not want to allow it for whatever reason.
3) Not all app data is moved, most of it is but some data is left on your phone so many people still run out of internal storage quickly.
4) You can force ALL apps to be moved to this area by default, but it breaks incompatible ones - such as Widgets, which are unable to load due to the SD card not being "prepared".
So that's Froyo's version. Before Froyo existed, some very clever people came up with a thing called "Apps2SD". Remember I said that your SD card normally is one big FAT32 partition? Well, Apps2SD works by having your SD card patitioned into TWO filesystems. A normal FAT32 partition for your usual stuff and a secondary "EXT" partition. EXT is just a filesystem, like FAT32 or NTFS, but it's the filesystem used by Android internally. The SD card is normally FAT32 because it's a "universal" filesystem, that just about any machine will be able to read, whereas EXT filesystems are generally Linux only, but I digress.
EXT has several different versions. The most common one you'll see is ext3. The main difference between ext2 and ext3 is "journaling", which is just a fancy way of saying that should an operation (such as copying, writing or reading) be interrupted unexpectedly (say, by you turning your phone off), then no data should be lost or corrupted. You know how when you turn your phone on, it says "preparing SD card"? It takes a few minutes, but what it's actually doing is checking that the FAT32 partition hasn't been damaged, because FAT does NOT have journaling. If you used a computer back in the Windows 98 days, you may remember that lovely blue "Scandisk" screen that had to run every time you didn't shut your computer down correctly - that's the same thing. But then Windows 2000/XP came along with NTFS, which also has journaling, meaning you had less chance of loosing data. But I digress once more.
So you have your SD card partitioned into EXT and FAT32. Generally it doesn't matter if it's ext3 or ext4, but you don't get any real advantage with ext4 over ext3 in this instance. Apps2SD then runs a special script on your phone which "symbolically links" the folder from your phone's internal storage where your apps are normally stored, to the ext partition on your SD card. A symbolic link is a bit like a shortcut for folders, except it's transparent to the OS: In other words, Android doesn't know that when it's installing it's apps to the internal phone storage, it's actually being stored on the SD card. This effectively boosts your internal phone memory from the previous 5mb that you had in my example above, up to whatever size you made the ext partition on your SD card (often 512Mb or 1Gb, but it depends on how many apps you install).
Plus, because it's "journaled", it doesn't need to be "prepared", meaning it's ready to go as soon as the phone starts - so your widgets and apps work immediately (unlike "forced" Froyo Apps2SD, where widgets disappear).
The catch with Apps2SD is that whatever space the ext partition takes up is taken away from the SD card. So if you have a 4Gb card (with something like 3.5Gb of actual storage) and you make a 512Mb ext partition, your SD card will "shrink" to 3Gb. The space isn't actually lost, it's just being used by the ext partition. If you reformat your card, you'll get it back.
Finally, there's a difference between "Apps2SD" and "Apps2SD+". Remember I said that your apps are stored on a special folder inside your Phone's NAND storage? Well, that was a bit of a lie. It's actually stored in TWO places. There's a second area which is called the Davlik Cache. You don't really need to worry about what this is for (Hint: IT's to do with the Java runetime your phone uses to run apps), all you need to know is that apps use it to store data, which also eats up internal phone memory. Apps2SD+ moves davlik cache to the ext partition on your SD card as well, freeing up even more space. Some people believe that this may come at the cost of performance, as the internal NAND memory should be faster than your SD card (Which is why you also get people arguing over which "class" SD card is better for Apps2SD - the logic being that a faster SD card means less impact from this move), but the truth of the matter is that your applications will be running from your Phone's RAM anyway, so performance isn't really impacted at all. Since most apps are only a few hundred Kb's in size, or a couple of MB at the most, it's a non-issue.
Finally, any recent version of Apps2SD/Apps2SD+ should work with an SD card that is or isn't formatted with an ext partition. It'll check for this partition when your phone first boots and if it's not there, just use internal phone storage.
Having an ext partition WITHOUT Apps2SD+ shouldn't cause any issues, either, so you can format your SD card whenever you're ready.
So in summary:
Apps2SD "fakes" your phone's internal memory and puts it all on a hidden section of your SD card.
Apps2SD+ pushes even more content to the SD card, freeing up even more space on the phone itself.
"Froyo" Apps2SD has various limitations that "old" apps2SD does not, but is much easier to handle as it doesn't involve any kind of "partitioning".
Click to expand...
Click to collapse
first, please consider the wording "app2sd+" used above can also be applied to "data2sd+" which should be the main purpose of this thread, because they are similar as they both use the sd-ext partition to store things. the only different is that app2sd+ only moves /data/app and dalvik cache but data2sd+ moves the entire /data partition
now based on my experience of how did i solve my bootloop problems even i install over 300 apps, is, not to integrate Froyo app2sd and app2sd+(or your data2sd+) then things will be fine.
as ive seen that voyager you have "moved all apps to sd" with froyo app2sd while you are TOGETHER using the script of app2sd+(or data2sd+). from the above explanation, your apps and data are now SHARED among /sd-ext and /sdcard/.android_secure which MAY lead to problems on our phones when it enters the process system after going through the bootanimation.
still remember the days and things we have discussed? it was in november when we first known each other i think my founding still applies to data2sd+
voyager20021 said:
For bootloops on Miks CM7 fist post he says
If you get bootloop or stuck at LG logo do next:
Sometimes Recovery can't format /system so you need to clear /system manually. You can do it with this zip (flash as always in recovery), or in mounts menu (clockworkmod recovery only), or with adb:
1. Mount /system in recovery.
2. adb shell rm -rf /system/*
You get 1 error. This is ok.
Will update if I found this bug.
Anyone tried that zip or adb fix? I am not so familiar with adb shell. The zip i think is incompatible or smth.
Franco, do you know if this has something to do with random reboots caused by moving too many apps to sd?
Click to expand...
Click to collapse
Miasmic said:
me.
that successfully wiped system partition and 2 months ago i did full wipe (including /system) and reinstall everything then do the same thing, and i got the same results - bootloop
please go to darktremor's main thread (nexus one dev forum) and scroll a few pages back, ive been yelling there for help and they did a lot to help me especially temasek(u know who? a famous n1 developer)....
but finally we got no conclusions trying everything, even switching to s2e had ****ed up my phone.
what solution i can tell is that
fk kernel + mik + dt a2sd script 2.7.5.2-1
+ apps staying on /EXT (shown "on phone")
= no problems
fk kernel + mik + dt a2sd script 2.7.5.2-1
+ apps staying partly on /EXT and partly on /android.secure (shown "on SD card")
= after booting (seen lockscreen) for about 3mins, the phone goes back to bootanimation and boot again
[im sure voyager is asking about this]
p.s. fk kernel + mik + dt 2.7.5.3 beta4
will result in LG logo stuck every 2 reboots. wipe /system no help.
hope my info is useful and yeah, take alook at the dt thread
until now the only solution is not to move apps partly to /android.secure
Sent from my LG-P500 using XDA Premium App
Click to expand...
Click to collapse
franciscofranco said:
Why move apps to sd card instead of /ext? doesn't make any sense............. No wonder **** happens...
Click to expand...
Click to collapse
Miasmic said:
Yea I agree with your point, moving the app only to /ext is apparently a safer method than dividing it into /ext and /android.secure
But however this method (using darktremor together with froyos a2sd feature) can save even more internal storage on our phones because darktremor doesn't move 100% of the "app" to /ext. Except "app data" , a small portion of "app" is also occupying the internal storage when using dartremor.
Say angry birds, despite its ~500kb /data size, when using darktremor, 18mb its "app" is moved to /ext while 2mb of it is staying in the internal storage. When using froyos a2sd feature, this 2mb is moved to /android.secure therefore even more internal space is free-ed.
According to the main darktremor thread, a user named bassmadrigal and even temasek himself, has stated that integrating darktremor "move to EXT" and froyos "move to FAT" does not produce any problems (at least on their nexus one) and can save even more space.
Well its not a problem for me as I only move 4 of my biggest apps to FAT and not having issues now.
I think voyagers attempting to move a lot of his apps (partly as they still partly stay at /ext) to /android.secure (as I tried before) and he got ****ed up like me before.
Hmmph I am not quite sure, voyager have you tried the same procedure (restore titanium and move them to FAT) without flashing Franco.kernel and only with the ROM (ans default kernel) and darktremor script installed? In that way we can see whether the "issue"(not at all but just an disadvantage of not supporting a feature) is about Franco's kernel or about our phones. cheers!!
Sent from my LG-P500 using XDA Premium App
Click to expand...
Click to collapse
franciscofranco said:
Just don't mess with the part that stays in the phone, if you do you're on your own, it's just too damn obvious to waste my time with it, sorry :/
Click to expand...
Click to collapse
Miasmic said:
yea, i definitely dont think it is of any priorities to request you to dig on this stuff and please dont, lol
was just telling my experiences to others and esp. voyager
Sent from my LG-P500 using XDA Premium App
Click to expand...
Click to collapse
yea, franco also said we shouldn't use the froyo app2sd function when we have already moved stuffs to the /sd-ext using app2sd+/data2sd+
therefore to prevent such abnormal behaviours on our phones we should treat our phones as Android 2.1 or before which does not have the capabilities to use froyo app2sd function to move things to /sdcard/.android_secure instead we should just let them be moved to the /ext partition.
i can confirm that yes there will still be decrease in internal storage because even you got data2sd+, there are something that cannot be moved from the internal storage to /sd-ext and we dont know what. JUST be fuxking sure that all your apps are stayed in "internal storage" (thats a way to fake the phone! you know) and they will be very safe in /sd-ext.
you may also like to install app2sd app but reverse the original concept of this app, i.e. to confirm NO APPS ARE EXISTING IN THE 2nd TAB (ON "SD CARD" with froyo function)
so, to test this out quickly, you may simply:
make proper partitions
wipe properly
flash rom
flash your a2sd+/data2sd+ script
boot phone
run the proper commands (for dt now i would dl a2sdgui and apply stuffs and let it reboot)
now restore titanium backup with INSTALL LOCATION set as "internal storage"
(in CM7 settings > application you may also choose "internal storage" to make sure everything is PURELY moved to /sd-ext instead of sharing among /sdcard/.android_secure with the froyo a2sd function) (however what i can tell you that this CM7 function is not working properly at least with my DT a2sd+ script therefore we have to double check whether it is in "INTERNAL STORAGE" when we install a new app) so now app2sd app came in handy remember is to reverse all apps to internal but not move them to so-called sd which was the original purpose of this app.
ok hope you understand what i meant and now you should not have bootloops
Under the hood
however, some users have reported that they have NO problems at all when they share their apps among /sd-ext and /sdcard/.android_secure. an example was bassmadrigal (located in the darktremor official thread)
maybe, it is phone specific. maybe, they have shared a less amount of apps as i myself can also confirm that the bootloop problems only occur if we SHARE A CERTAIN AMOUNT OF APPS among the two places.
and for your safety, at least to first eliminate the bootloops problems before doing any experiments, still follow the above and MOVE ALL OF THEM TO so-called "INTERNAL" (pure /sd-ext)
so you mean to say that keep all the apps in internal memeory and it will be safe in sd-ext with any a2d script rather than moving into sdcard?
There is one script i am tryingvhttp://forum.xda-developers.com/showthread.php?t=1342387. I dont have any script installed.But it is still giving me bootloops.
williamcharles said:
so you mean to say that keep all the apps in internal memeory and it will be safe in sd-ext with any a2d script rather than moving into sdcard?
There is one script i am tryingvhttp://forum.xda-developers.com/showthread.php?t=1342387. I dont have any script installed.But it is still giving me bootloops.
Click to expand...
Click to collapse
yes, the message i would like to bring is rather simple and easy but most of the users are confused about "move to ext" and "move to FAT" and the BUTTON in the application manager of our phones show "MOVE TO SD" which is moving PART of the app to SD-FAT (android.secure) so they are now SHARED and will produce PROBLEMS.
This important point is what most of the script developers have forgotten to warn their users.
Remember to check your settings and ROM/kernels/partitions/scripts compatibility with each other before regarding the script solely as the cause of any problematic behaviour (best way to prove is to see whether there are someone using the same combination without problems
then, install the script, and start installing apps only into "internal storage" (to fake your phone as they actually goes to /sd-ext) and NEVER EVER touch the button "Move to SD" in the application manager then you should be fine as said in my first post, double check they are in the internal storage after you have grabbed a new app from market it will be fine to move it back to "internal storage" as long as you havnt reboot the phone.
Miasmic said:
yes, the message i would like to bring is rather simple and easy but most of the users are confused about "move to ext" and "move to FAT" and the BUTTON in the application manager of our phones show "MOVE TO SD" which is moving PART of the app to SD-FAT (android.secure) so they are now SHARED and will produce PROBLEMS.
This important point is what most of the script developers have forgotten to warn their users.
Remember to check your settings and ROM/kernels/partitions/scripts compatibility with each other before regarding the script solely as the cause of any problematic behaviour (best way to prove is to see whether there are someone using the same combination without problems
then, install the script, and start installing apps only into "internal storage" (to fake your phone as they actually goes to /sd-ext) and NEVER EVER touch the button "Move to SD" in the application manager then you should be fine as said in my first post, double check they are in the internal storage after you have grabbed a new app from market it will be fine to move it back to "internal storage" as long as you havnt reboot the phone.
Click to expand...
Click to collapse
Miasmic said:
yes, the message i would like to bring is rather simple and easy but most of the users are confused about "move to ext" and "move to FAT" and the BUTTON in the application manager of our phones show "MOVE TO SD" which is moving PART of the app to SD-FAT (android.secure) so they are now SHARED and will produce PROBLEMS.
This important point is what most of the script developers have forgotten to warn their users.
Remember to check your settings and ROM/kernels/partitions/scripts compatibility with each other before regarding the script solely as the cause of any problematic behaviour (best way to prove is to see whether there are someone using the same combination without problems
then, install the script, and start installing apps only into "internal storage" (to fake your phone as they actually goes to /sd-ext) and NEVER EVER touch the button "Move to SD" in the application manager then you should be fine as said in my first post, double check they are in the internal storage after you have grabbed a new app from market it will be fine to move it back to "internal storage" as long as you havnt reboot the phone.
Click to expand...
Click to collapse
Much simpler explained. We'll have to test your theory. Only now i use ungaze's script which is something like "everything2sd". The button reading move to sd or move to internal has no influence at all. And still having bootloops at some point. Only now the sd ext is 2Gb max, though it never got to fill it without that damn bootloop.
Thanks again MIASMIC for addressing one of the biggest remaining problems which keep us away from having a PERFECT AND COMPLETE O1, now when we are close to having the stable official CM7 and official or not CM9 which will bring so many and awsome STABLE ROMs based on those 2.