Related
I have rooted my optimus one.
just wanna know which are d apps that are neCessary to remain in the phone memory.
so that i cn move rest to sd.
Widgets should remain in the phone memory. Everything else that doesn't run frequently should go to the SD card
kpbotbot said:
Widgets should remain in the phone memory. Everything else that doesn't run frequently should go to the SD card
Click to expand...
Click to collapse
What about keyboards,go sms,maps n youtube??
Oh yea. I forgot about those. Keyboards and go sms. I think it's okay to move youtube and maps onto the sd card
kpbotbot said:
Oh yea. I forgot about those. Keyboards and go sms. I think it's okay to move youtube and maps onto the sd card
Click to expand...
Click to collapse
K.
unable to move maps n youtube.
stil woried abt lockscreen n launchers.
Are you using the stock ROM? Apps that are in /system/app cannot be moved to the SD. If you installed it via downloading/installing from the market or somewhere else, you can move it.
Everything that feels like it should be launched no matter what or those that need to be started quickly on boot, keep it on the phone memory.
kpbotbot said:
Are you using the stock ROM? Apps that are in /system/app cannot be moved to the SD. If you installed it via downloading/installing from the market or somewhere else, you can move it.
Everything that feels like it should be launched no matter what or those that need to be started quickly on boot, keep it on the phone memory.
Click to expand...
Click to collapse
Yeah. m on stock.
did move sum apps to sd via app 2 sd enabler.
Cmon guys I thougjt it was safe to move all sh#t to sd
It's safe. It's just that apps that need to be started on boot must be there as soon as it can. Read and write speeds on the SD card is much slower than on the phone memory.
Well he didnt ask for fast boot
It's not about fast booting It's about getting the things you need as fast as you can. For example, I need a widget to load as fast as it can since it has to be there as soon as the phone boots. That was my point
Everything that you don't use everyday move to SDcard (if possible). If you move favourite apps to SD and you acces them all day long you will shorten the SDcard's life.
I have void with a2sd enabled. So all user applications are on sd. Can I use titanium backup to move some apps to internal memory?
lekhwani said:
I have void with a2sd enabled. So all user applications are on sd. Can I use titanium backup to move some apps to internal memory?
Click to expand...
Click to collapse
I used Titanium to move a lot of stuff over to the SD from Internal... Stuff in the /system directory doesn't affect your phone's "Internal Storage Space" as reported in the Settings menu since /data and /system are separate partitions. Apart from /system apps, the only thing that I would want to move to the SD that it couldn't move was the PayPal App from the app-private location. Going into ADB wouldn't allow me to do it either.
Titanium also allowed me to uninstall a bunch of the **** that came installed like game demos. This did not free up additional storage space, with the exception of what it removed from Dalvik-Cache. Which, btw is going to be your biggest issue... Some ROM's allow you to move this to the /cache partition, but this is a relatively small partition (~56MB) on this phone and my Dalvik-Cache currently takes up ~90MB.
Pls reply here guys.
http://forum.xda-developers.com/showthread.php?t=941156
I use app 2 sd to move everything I dont need frequently on SD, than just long press on those program from app 2 sd and Open them.
It's a bit tricky and I dont know other ways (on the home screen most of SD apps wont appear...) but I never had slow opening and the like
Everything was ok till xtesterday.
today i rebooted ma cell,
and all d apps disappeared of sd.
though sd is accessible via file manager,gallery.
i tried formattingsd,cell reset.
bt all in vain.
cant install from file manager.
cant even install from market.
even unable to unmount ma card.
any solution???
Jason_V said:
I used Titanium to move a lot of stuff over to the SD from Internal... Stuff in the /system directory doesn't affect your phone's "Internal Storage Space" as reported in the Settings menu since /data and /system are separate partitions. Apart from /system apps, the only thing that I would want to move to the SD that it couldn't move was the PayPal App from the app-private location. Going into ADB wouldn't allow me to do it either.
Titanium also allowed me to uninstall a bunch of the **** that came installed like game demos. This did not free up additional storage space, with the exception of what it removed from Dalvik-Cache. Which, btw is going to be your biggest issue... Some ROM's allow you to move this to the /cache partition, but this is a relatively small partition (~56MB) on this phone and my Dalvik-Cache currently takes up ~90MB.
Click to expand...
Click to collapse
I used Titanium again and used it to incorporate the updated GApps into the ROM. I knew that I had about 56MB free on the system partition. Putting Gmail, Maps, Street view, Market and anything else that I could find freed 30MB on the data partition.
Goofy problem but every rom I have tried will not update tweetdeck properly in the background with the screen black, except for xtrsense. Even the original stock rom does not work properly at doing this. Has anyone else had the same problem? Is there a fix?
I would love to be able to go to one of the 2.2 or 2.3 roms but i need tweetdeck to update properly on my accounts.
Side question - will there be a 2.2 or 2.3 for xtrsense?
Side question 2 - I am going to be searching for this but figured i would throw it in just incase I can not figure it out. I loaded the gscript for the apps2sd but I cant get any apps to the sd card. It is not even an option when I go to the manage apps. Like I said, I am going to search for this one but while I was typing I figured I would throw it in.
Tweetdeck is one of my key apps and I have no trouble at all with it on CELB Froyo or GSB. The only ROM I had an issue with was a later version of Nonsensikal. For some reason, that had an Autokiller-like aggressive memory setting and Tweetdeck would not stay open in the background.
Unlike many other twitter clients, Tweetdeck has no way to autostart and seems to have no server component to get updates, and aggressive memory settings will close the app when it is in the background. If you are using autokiller or something like it, using the optimum preset seems to work pretty well. Just vanilla GSB settings are just fine.
KnightRid said:
Side question - will there be a 2.2 or 2.3 for xtrsense?
Side question 2 - I am going to be searching for this but figured i would throw it in just incase I can not figure it out. I loaded the gscript for the apps2sd but I cant get any apps to the sd card. It is not even an option when I go to the manage apps. Like I said, I am going to search for this one but while I was typing I figured I would throw it in.
Click to expand...
Click to collapse
Gscript for Apps2SD? I never heard of a GScript for that capability. There's an Apps2SD flashable zip which adds the Apps2SD script to your phone, if that's what you're talking about, but you don't use it in GScript.
Technically and completely literally, there never can be a 2.2 or 2.3 version of xtrSENSE because xtrSENSE is (currently) based on the July OTA 2.1, so it's a heavily modified version of THE official ROM for the Eris. There is no official 2.2 or 2.3 for the Eris, so there's no 2.2 or 2.3 stock ROM with Sense to base a new Eris ROM on.
Devs have worked on 2.2 and 2.3-based Sense ROMs based on stuff from other phones, but none of them are as stable and "finished" as the original stock ROM, or even xtrSENSE. Things don't work such as Wifi and Camera, and possibly some other difficulties. They haven't given up but they've been beating their heads against the wall for months for Froyo Sense. At this point, there's probably a marginally better chance that we'll ever have a port of a Gingerbread Sense which has everything working, over Froyo Sense.
doogald said:
Tweetdeck is one of my key apps and I have no trouble at all with it on CELB Froyo or GSB. The only ROM I had an issue with was a later version of Nonsensikal. For some reason, that had an Autokiller-like aggressive memory setting and Tweetdeck would not stay open in the background.
Unlike many other twitter clients, Tweetdeck has no way to autostart and seems to have no server component to get updates, and aggressive memory settings will close the app when it is in the background. If you are using autokiller or something like it, using the optimum preset seems to work pretty well. Just vanilla GSB settings are just fine.
Click to expand...
Click to collapse
I use advanced app killer but i do not let that run all the time, I just start it when I want to manually kill apps.
It is just so weird with tweetdeck not updating in the background right, except on xtrsense. I just dont get it
roirraW "edor" ehT said:
Gscript for Apps2SD? I never heard of a GScript for that capability. There's an Apps2SD flashable zip which adds the Apps2SD script to your phone, if that's what you're talking about, but you don't use it in GScript.
Click to expand...
Click to collapse
Yes, he has a gscript script built in to xtrsense that you can just load and run to do it.
I will have to redo my sdcard again and see if that fixes it. I still like how 2.3 lets you move the apps though. It is a WHOLE lot easier.
KnightRid said:
Side question 2 - I am going to be searching for this but figured i would throw it in just incase I can not figure it out. I loaded the gscript for the apps2sd but I cant get any apps to the sd card. It is not even an option when I go to the manage apps. Like I said, I am going to search for this one but while I was typing I figured I would throw it in.
Click to expand...
Click to collapse
That's not how it works with xtrSENSE. With xtrSENSE, you first need to partition your SD card to add an ext3 partition to store your apps. Then, as you noted, you run a gscript to activate apps2sd. This will move *all* of your user apps to the ext partition - you cannot choose to keep some internal. You either have your apps internal and not on SD, or you have your apps on SD and not internal.
The original post in the xtrSENSE thread explains this pretty well. The relevant portions are here:
Apps2sd and Cache2sd:
I have revamped my implementation of apps2sd to use simpler and better organized scripts. For apps2sd to work you must first complete the listed prerequisites and it is a good idea to read through the "things you may want to know about apps2sd" section. Although it can provide gobs of space for apps, Apps2sd is not for everyone as it ties the stability of your phone to your SD card... If you do not need the space I would recommend that you keep the default of DISABLED; if you want to try you can always disable it again however there is always the chance of issues.
To enable/disable apps2sd and cache2sd just run the appropriate GScript and reboot your phone (Quick Boot makes this easy!).
Prerequisites
If you have not setup your SD card (for those new to Apps2sd) as per tkirton:
BACKUP YOUR SD CARD TO YOUR COMPUTER. Can't stress this enough, as partitioning will wipe the entire card.
Reboot into recovery
In Android System Recovery, select Partition sdcard
In the Partition sdcard menu, select Partition SD
Follow the instructions on the phone to partition your SD card. Most folks seem to recommend using the default values however you can go larger or smaller use values 256, 512,768,1024. You will also be asked to set a swap size; I stayed at 32mb (anticipate future ROM options to allow moving swap to sd)
Once the partition is initially created you must then convert to ext3 - In the Partition sdcard menu, select SD:ext2 to ext3. Follow the instructions on the screen.
Press the back button on the phone to go back to the main menu.
Your SD card is now ready to work with an Apps2sd supported ROM.
Things you may want to know about apps2sd
Bootloop protection is built in if your SD card is corrupted or is removed from the phone with Apps2sd enabled. Your apps will go away but your phone will boot .
There are 3 subsets of data associated to an app when it is installed and run on your phone.
1) /data/app/ (and /data/app-private) - actual .apk files we think of as the applications that are not system apps (i.e. installed on /system/app)
2) /data/data/ - the files produced by ALL apps (system apps and market apps) during installation that are used by the Android system to run the app
3)/data/dalvik-cache/ - app cache file and work space for ALL apps (system apps and market apps).
From root explorer (or similar) you can browse to the /data/app OR the /system/sd/app folders and you will see the same thing, both will tell you how much space you have used and have left. The way apps2sd works is by "linking" the /system/sd/app to the /data/app folder so that the Android system thinks it is accessing the /data/app it is really at /system/sd/app.
I have seen using Apps2sd cause issues with some.zip flash updates as they try to write directly to the /data/app folder which no longer "physically" exists
If you get into a bootloop issue using apps2sd boot into amon_ra recovery and try one of the follow:
1) from the Other menu option select the Fix apk uid mismatches
2) from the Wipe menu option complete a)Wipe data/factory reset b)Wipe Dalvik-cache c)Wipe SD:ext partition
Apps2sd and Cache2sd Basics
When you run the apps2sd or cache2sd script, upon reboot, it will move ALL your existing apps or cache to the sd card ext partition and ALL future apps and cache will be installed and stored on the sd card ext partition.
Running the apps2internal or cache2internal script, upon reboot, it will move ALL your existing apps or cache to the /data block of internal storage and ALL futures apps and cache will be stored in internal storage.
With HTC based ROMs it is all or nothing and you cannot move individual apps like in the CyanogenMod ROMs.
So how do I know Apps2sd is on? - You can run the GScript report_system_stats which will give you a printout of what fileblocks are used as well as a “true/false” value for Apps2sd On. You can also go to menu>Settings>Sd card and phone storage - when on space available under Available storage will go down at a VERY slow rate when new apps are installed.
Click to expand...
Click to collapse
Note the parts that I bolded.
KnightRid said:
I use advanced app killer but i do not let that run all the time, I just start it when I want to manually kill apps.
It is just so weird with tweetdeck not updating in the background right, except on xtrsense. I just dont get it
Click to expand...
Click to collapse
It works fine for me on xtrSENSE. Try uninstalling advanced app killer for a while and see if tweetdeck works better. Also, run the gscript set_memory_balanced or set_memory_stock. I have had Tweetdeck work just fine in xtrSENSE4.6.5 with both of those settings.
doogald said:
That's not how it works with xtrSENSE. With xtrSENSE, you first need to partition your SD card to add an ext3 partition to store your apps. Then, as you noted, you run a gscript to activate apps2sd. This will move *all* of your user apps to the ext partition - you cannot choose to keep some internal. You either have your apps internal and not on SD, or you have your apps on SD and not internal.
Click to expand...
Click to collapse
I did not explain well, I did do that but the apps still would not move over. I thought i had to manually move the apps after the ext3 partition and such but there must be something little I am missing. I will go back through the steps again and see what happens. I still like how 2.2 and 2.3 move the apps a lot better and I wish xtrsense would be based on 2.2 or 2.3
As for tweetdeck, it DOES work right in xtrsense just not in any other rom even the stock rom.
KnightRid said:
I did not explain well, I did do that but the apps still would not move over. I thought i had to manually move the apps after the ext3 partition and such but there must be something little I am missing.
Click to expand...
Click to collapse
When you run that gscript that I highlighted above (report_system_stats), does it say that you have apps2sd enabled? If it does, then you do. After you partition your card and run the gscript to enable apps2sd (called apps2sd), there is nothing that you need to do manually - the apps will move to SD. All new apps that you install will go to SD. You cannot pick and choose - apps are either on SD or internal.
I will go back through the steps again and see what happens. I still like how 2.2 and 2.3 move the apps a lot better and I wish xtrsense would be based on 2.2 or 2.3
Click to expand...
Click to collapse
To be honest, I think that this method is better. For one thing, you can back up your ext partition on your SD card; unless you use Clockwork, you cannot backup .android_secure. Also, when you connect your SD card to your computer, it dismounts the SD card from the phone, making those apps unavailable until you re-mount the SD card to the phone. Because you cannot dismount the ext3 partition (without trying really hard, that is), your apps are always available. Widgets can run from those apps. Lastly, there is no this app is internal, that app is on SD - they are either all on SD or they are not. Plus, of course, you don't have to move apps one at a time.
doogald said:
When you run that gscript that I highlighted above (report_system_stats), does it say that you have apps2sd enabled? If it does, then you do. After you partition your card and run the gscript to enable apps2sd (called apps2sd), there is nothing that you need to do manually - the apps will move to SD. All new apps that you install will go to SD. You cannot pick and choose - apps are either on SD or internal.
Click to expand...
Click to collapse
Yea, it just doesnt move anything for some reason - Really isnt that big of a deal just would be nice with me being a packrat for everything so I wouldnt have to uninstall as often lol
Thanx for the help!
I am still wishing and hoping for xtrsense based on 2.2 or 2.3 though =)
doogald said:
That's not how it works with xtrSENSE. With xtrSENSE, you first need to partition your SD card to add an ext3 partition to store your apps. Then, as you noted, you run a gscript to activate apps2sd. This will move *all* of your user apps to the ext partition - you cannot choose to keep some internal. You either have your apps internal and not on SD, or you have your apps on SD and not internal.
The original post in the xtrSENSE thread explains this pretty well. The relevant portions are here:
Note the parts that I bolded.
It works fine for me on xtrSENSE. Try uninstalling advanced app killer for a while and see if tweetdeck works better. Also, run the gscript set_memory_balanced or set_memory_stock. I have had Tweetdeck work just fine in xtrSENSE4.6.5 with both of those settings.
Click to expand...
Click to collapse
There's an app called Link2SD which allows you to use old-school Apps2SD with the ability to only move what you want to move. Haven't tried it but reports are positive about it. Creates symlinks or some such for individual apps instead of for the whole data/app folder at once.
doogald said:
When you run that gscript that I highlighted above (report_system_stats), does it say that you have apps2sd enabled? If it does, then you do. After you partition your card and run the gscript to enable apps2sd (called apps2sd), there is nothing that you need to do manually - the apps will move to SD. All new apps that you install will go to SD. You cannot pick and choose - apps are either on SD or internal.
To be honest, I think that this method is better. For one thing, you can back up your ext partition on your SD card; unless you use Clockwork, you cannot backup .android_secure. Also, when you connect your SD card to your computer, it dismounts the SD card from the phone, making those apps unavailable until you re-mount the SD card to the phone. Because you cannot dismount the ext3 partition (without trying really hard, that is), your apps are always available. Widgets can run from those apps. Lastly, there is no this app is internal, that app is on SD - they are either all on SD or they are not. Plus, of course, you don't have to move apps one at a time.
Click to expand...
Click to collapse
There's a couple of apps on the market, Dual Mount SD (used to be called SD Share, I think) and Multi Mount SD, which now, not only allow you to mount your SD card to both your computer and your phone at the same time, they also both have the option to auto-mount your SD card to your computer when you plug it in to the USB cable, which is now what I do. Multi Mount SD had that feature first, Dual Mount SD copied it just recently.
Also, Titanium Backup (paid, don't know about the free version) will allow you to batch move as many apps as you like to and from the SD card.
roirraW "edor" ehT said:
There's a couple of apps on the market, Dual Mount SD (used to be called SD Share, I think) and Multi Mount SD, which now, not only allow you to mount your SD card to both your computer and your phone at the same time, they also both have the option to auto-mount your SD card to your computer when you plug it in to the USB cable, which is now what I do. Multi Mount SD had that feature first, Dual Mount SD copied it just recently.
Also, Titanium Backup (paid, don't know about the free version) will allow you to batch move as many apps as you like to and from the SD card.
Click to expand...
Click to collapse
Good to know, but I still like the "old school" apps2sd kludge more than the official kludge that Google added with Froyo. I've had more problems with apps2sd (when I tried it) with Froyo than I ever had with xtrROM before cache2cache was added to that ROM.
doogald said:
Good to know, but I still like the "old school" apps2sd kludge more than the official kludge that Google added with Froyo. I've had more problems with apps2sd (when I tried it) with Froyo than I ever had with xtrROM before cache2cache was added to that ROM.
Click to expand...
Click to collapse
The absolutely only thing I don't like about, now that Link2SD is out, is that it's difficult to use the old Apps2SD under Froyo and beyond, requiring special partitioning arrangements, concerning where the particular partitions are and making it difficult to mount all the Fat32 partitions to both the phone and the computer, unless there's been progress in those areas I haven't been made aware of.
Even though there's some things which won't move to the SD card in a friendly way with Froyo's move to SD, almost everything will move if you use an app such as Titanium Backup to move them. As I said, there's still some apps it won't move but it moves almost all of them for me. I guess I wouldn't like it if I was stuck with Google implementation of it, but as long as there are third party apps to make up what it's lacking, it works great for me.
I also like that since I "only" have an 8GB SD card, that I don't have to partition it, the apps that are moved to SD will only take up as much space as they need to, no partition with space that'll never get used because I want it at least large enough to cover my worst case scenarios.
Off topic, it's unbelievable how much "crap" I get on my SD card, from all the apps I've stopped using but never deleted any respective folders for from the card. Mostly because I replaced the app with something better.
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.
Hi,
I did a backup using Titanium Backup and Go Backup and after wiping my Motorola Defy, tried to restore apps, contacts etc.
The problems I encountered were:
1) Go Backup can't recognize backup directory on SD card for some reason.
2) Can't move apps to SD. An error occurs: "Move Application: Failed to move application. There is not enough storage left." Needless to say, I have more than enough storage.
This is was I encountered by far, although I believe these are just a small part of the symptoms for a single problem.
Maybe its because there are no permissions, or moving apps is impossible because of an existing app files on the SD card.
Does anyone know what is the actual cause for this?
Or is there a tool to fix the permissions on the Defy?
Thanks ahead!
See if any of your other partitions are full or close to full.
post-mortem said:
See if any of your other partitions are full or close to full.
Click to expand...
Click to collapse
I have no partitions on my SD card
No, I mean the internal memory of the device.
post-mortem said:
No, I mean the internal memory of the device.
Click to expand...
Click to collapse
Does it has to do with the moving app to the SD card?
And it seems I do have a little space for apps, but how should I check it anyway?
The easiest way is to run Link2SD -> menu -> Storage Info
This will show all the mounted partitions, and space used/free.
post-mortem said:
The easiest way is to run Link2SD -> menu -> Storage Info
This will show all the mounted partitions, and space used/free.
Click to expand...
Click to collapse
Internal: 103mb used, 25mb free
SD: 8.71gb used, 6.12gb free
SD 2nd: not found
System: 178mb used, 148mb free
Cache: 16.29mb used, 177mb free
No idea?
I tried that:
1) Deleted the GO Backup directory
2) Removed the app
3) Re-installed the app
4) Copied back the backup from my PC
I could then see use the backup, but I still can't move apps to SD
Something must be jamming it
Can it be something with the mounts?
I haven't used Go Backup, so I have no experience with it, but it does seem that it's somehow involved/responsible. I noticed they have an update as of yesterday, so you can see if it makes any difference.
Have you tried putting your SD card into your computer? Does it function normally? Can you run a disk check on the card from your computer?
post-mortem said:
I haven't used Go Backup, so I have no experience with it, but it does seem that it's somehow involved/responsible. I noticed they have an update as of yesterday, so you can see if it makes any difference.
Have you tried putting your SD card into your computer? Does it function normally? Can you run a disk check on the card from your computer?
Click to expand...
Click to collapse
The problem is not with GoBackup, as it works now.
The problem must be with something jamming access to the SD card.
I tried to run a check from my PC and I get "No problems found"
And now, for some reason the phone activity crashes after I terminate a call
Well, all the applications I installed where installed using Titanium Backup.
While trying to install from Play Store, the device crashes.
It uses CM 7.2.
So it might be a permission problem in the device itself.
Well, i tested this for some roms and its the same on all of them:
if i move apps that are app2sd-capable by native to sd (via settings -> apps), they work fine, they are still there after reboot.
but if i move apps (app2sd-capable by native or not) via link2sd (yes, moving via link2sd, NOT LINKING!!) or titanium backup, they are all there and working, but after doing a reboot
they're gone.
anyone else experiencing this? what can i do to resolve that? :silly:
realCyphox said:
Well, i tested this for some roms and its the same on all of them:
if i move apps that are app2sd-capable by native to sd (via settings -> apps), they work fine, they are still there after reboot.
but if i move apps (app2sd-capable by native or not) via link2sd or titanium backup, they are all there and working, but after doing a reboot
they're gone.
anyone else experiencing this? what can i do to resolve that? :silly:
Click to expand...
Click to collapse
Why are you using a2sd? This device has enough memory.
To answer your question: The a2sd scripts are meant for Android 2.3.3- or low-end devices. It's likely it won't work
enough memory? well, not for me
im talking about the "most normal" method of moving apps to sd, via settings -> apps -> move app to sd
this works.
but doing so via link2sd or titanium backup doesnt after performing a rebooot.
and im pretty sure i did so (via link2sd) on some other ics-driven devices i owned so im just wondering why it wont work on the dx?
realCyphox said:
enough memory? well, not for me
im talking about the "most normal" method of moving apps to sd, via settings -> apps -> move app to sd
this works.
but doing so via link2sd or titanium backup doesnt after performing a rebooot.
and im pretty sure i did so (via link2sd) on some other ics-driven devices i owned so im just wondering why it wont work on the dx?
Click to expand...
Click to collapse
Are they really gone, or do they just not work?
realCyphox said:
enough memory? well, not for me
im talking about the "most normal" method of moving apps to sd, via settings -> apps -> move app to sd
this works.
but doing so via link2sd or titanium backup doesnt after performing a rebooot.
and im pretty sure i did so (via link2sd) on some other ics-driven devices i owned so im just wondering why it wont work on the dx?
Click to expand...
Click to collapse
Well, I'm not sure what you are doing with your phone but I have 50+ apps on it, 10+ games and some of them really big (like Real Racing 2 and NFS MW), none of them moved on sd card and I have 400mb of free space.
MaartenXDA said:
Are they really gone, or do they just not work?
Click to expand...
Click to collapse
they are gone from the app drawer and in settings -> apps they are greyed out and have this standard-android-symbol as icon.
when i check via titanium backup they are also not there, but titanium backup finds orphan data to delete, which are virtually useless remains from
those "former installed apps" if you wanna call them that
@nlooooo
its just about having the option do so. i had that on my previous phones and i would love to have that on the dx.
well, im thinking about using "normal" app2sd for apps that are movable natively and link2sd + sd-ext partition for apps that are not movable natively
i know its weird, but i like to keep my data partition as clean as possible
realCyphox said:
they are gone from the app drawer and in settings -> apps they are greyed out and have this standard-android-symbol as icon.
when i check via titanium backup they are also not there, but titanium backup finds orphan data to delete, which are virtually useless remains from
those "former installed apps" if you wanna call them that
@nlooooo
its just about having the option do so. i had that on my previous phones and i would love to have that on the dx.
well, im thinking about using "normal" app2sd for apps that are movable natively and link2sd + sd-ext partition for apps that are not movable natively
i know its weird, but i like to keep my data partition as clean as possible
Click to expand...
Click to collapse
You have to accept the fact that using link2sd and symlinking will slow down your phone.
I doesn't work because of /system write protection, so all sylinks made when phone is booted are deleted when phone is restarted, If you're able to make those symlinks in recovery it will work. You can try with script that disables write protection, but I'm still not sure why would you need any a2sd scrip.
While I had Desire I used a2sd scripts, but when I bought Incredible S I didn't have any need to use them anymore. The same is with DesX.
nlooooo said:
You have to accept the fact that using link2sd and symlinking will slow down your phone.
I doesn't work because of /system write protection, so all sylinks made when phone is booted are deleted when phone is restarted, If you're able to make those symlinks in recovery it will work. You can try with script that disables write protection, but I'm still not sure why would you need any a2sd scrip.
While I had Desire I used a2sd scripts, but when I bought Incredible S I didn't have any need to use them anymore. The same is with DesX.
Click to expand...
Click to collapse
apps moving to sd-ext works fine when using the write protection patch, tested that before, worked fine till i screwed my rom up because of some other stuff.
my problem is moving apps to sd, not linking them to a second sd-partition. i mean, if i move apps to sd via titanium even the apps that are definitely movable by "oldschool" app2sd are gone. thats the weirdest part i dont get.
so moving apps to sd via link2sd or titanium has to work somewhat different than doing so via apps -> settings or any "standard" app2sd app available in the market, doesnt it?
realCyphox said:
apps moving to sd-ext works fine when using the write protection patch, tested that before, worked fine till i screwed my rom up because of some other stuff.
my problem is moving apps to sd, not linking them to a second sd-partition. i mean, if i move apps to sd via titanium even the apps that are definitely movable by "oldschool" app2sd are gone. thats the weirdest part i dont get.
so moving apps to sd via link2sd or titanium has to work somewhat different than doing so via apps -> settings or any "standard" app2sd app available in the market, doesnt it?
Click to expand...
Click to collapse
I've never used titanium for that, but link2sd is moving them to sd-ext, creating symlinks, that's why that's not working. Using native app2sd from OS moves only .apk files to .android_secure folder on fat32 partition of sd card.
nlooooo said:
I've never used titanium for that, but link2sd is moving them to sd-ext, creating symlinks, that's why that's not working. Using native app2sd from OS moves only .apk files to .android_secure folder on fat32 partition of sd card.
Click to expand...
Click to collapse
no no, link2sd can move apps2sd OR/AND (if you have a second partition on your sdcard) can link them to sd-ext. it can do BOTH.
and as i said, LINKING apps works just fine when using the write-protection patch. but moving apps to "normal sd card partition" doesnt.
I have this problem before when using link2sd on my old phone.
Your second partition might be corrupt.
On which ext u created the second partition?
There are two you can choose, ext2 or ext3. If you created the second partition on ext3, when u open up the link2sd app choose ext3 at the first time, then all the apps u partitioned/linked on ext3will be visible again.
Ps. I don't think desire x need link2sd as 1gb is really a lot! Trust me u don't need it.
Sent from my HTC Desire X using xda app-developers app
again: i'm talking about moving (NOT LINKING) apps. link2sd can do that. and i have no second partition on my sdcard right now.
edited the first post and i hope noone will talk about linking apps anymore