Hi, when i had a HTC desire, which had not a lot more internal memory than our phones, there was a script on one of the roms, DATA2SD i think it was called, after partitioning your card, the internal memory could go up to 2GB i think (well, on my 16gb card anyway), can this be done n our phones? and do any roms have this????
Two steps: 1) Format 2) Choose script.
First you need to format your SD card so you have a FAT32 partition (first primary partition) and an EXT partition as the second primary partition. I do this from the commandline, but the best option is to use CWM V5+ which automates this for you. Then there are several options for scripts which mount the EXT partition as a virtual internal /data/app/ directory
S2E is the recommended option if you use a cyanogenmod based ROM. It uses mount points.
A2SD is installed by default on ROMs that use ketut's kernel if I remember correctly. It uses a simple symlink.
Link2SD is available for multiple ROMs. It is the most "advanced" as it links individual apps rather the whole directory, but with more power comes less simplicity...
Ahh the Desire.....a phone that is still popular despite its age
Herpderp Defy.
biggary said:
Hi, when i had a HTC desire, which had not a lot more internal memory than our phones, there was a script on one of the roms, DATA2SD i think it was called, after partitioning your card, the internal memory could go up to 2GB i think (well, on my 16gb card anyway), can this be done n our phones? and do any roms have this????
Click to expand...
Click to collapse
Peep my signature.
search a bit in general section
there is a thread
1 guy did it
but its only for stock roms
and btw why the hell did u go from htc desire 2 sga lol
Related
total noob
pretty sure it's not the developers fault of tazzsensefroyobt. because for a while it was working great for me. ever sense i tried to use apps2sd on PlainJaneT2_V2.0. i keep having an error on tazzsensefroyobt saying sd card is not mounted.
used rom manager to format sd card. then trying to fix this reformated using windows
There is a reason for that - the method to get apps2sd on a 2.1 ROM like PlainJane has you create a second partition on your SD card,to create a location to hold the apps. Unfortunately, Froyo will not mount an SD card with more than one partition.
You'll have to do these things, I think:
- backup your SD card
- do a Nandroid+ext backup from PlainJane, in case you want to go back
- follow the steps to partition your SD card from before, but choose 0 bytes for both the ext2 and swap partition sizes. This will erase your SD card
- go into the USB-MS option from Recovery to copy files back over to your formatted SD Card.
- Now you can flash the Froyo ROM you want
worked beautifuly thanks
apps2sd
so if i want to get rid of apps2sd on a 2.1 rom and just use for 2.2 roms just format with 0 on both swap size and ext2 size
monkeyboy19762 said:
so if i want to get rid of apps2sd on a 2.1 rom and just use for 2.2 roms just format with 0 on both swap size and ext2 size
Click to expand...
Click to collapse
That's correct. For some reason I think that there is one of the 2.2 ROMs that actually will mount an SD card with more than one partition, but I could be wrong about that, and I can't remember which one it is. But if a Froyo or Gingerbread ROM will not mount a perfectly good SD card with more than one partition? That's why - it has more than one partition.
doogald said:
That's correct. For some reason I think that there is one of the 2.2 ROMs that actually will mount an SD card with more than one partition, but I could be wrong about that, and I can't remember which one it is. But if a Froyo or Gingerbread ROM will not mount a perfectly good SD card with more than one partition? That's why - it has more than one partition.
Click to expand...
Click to collapse
Froyo and higher will work with multiple partitions; it's just not real easy. The trick is that the SD card has to be partitioned in a certain way.
From memory of the thread that's in the Dev section (I think the OP was Conap), the first partition has to be FAT32, and would have to be large enough for any NANDs and ROMs you want to ever backup/restore and flash.
Any other partitions can be anything you want BUT with this one rule. If you have a total of four partitions or less, then the last partition HAS to be FAT32, and will be the partition that'll be mounted by the AndroidOS when it's up and running. The second part of this rule is that if you have MORE than four partitions then the fourth partition is the one that has to be FAT32.
Just like partitions 2 and 3, anything from 5 and on can be anything you want. Conap also developed scripts to mount partitions like the first FAT32 one, since it's nice to have access to it from the running phone from time to time (mounting it through USB from Amon RA or Clockwork Mod should still work as normal). I think he also made ways to mount these other partitions from Windows. My memory is fuzzy. I only tried once to make this work for me, but I wasn't really successful mounting the oddball partitions to the phone or to Windows, and I didn't try real hard - I didn't care enough to really try to figure out what I assumed I did wrong, since I believe other people were able to test it just fine.
This theory of operation appeared to be developed in conjunction with the dual-boot AndroidOS 2.1/2.2 ROM by TeamAndIRC (I think they're called), which includes Conap and others as members. I never tried the ROM.
I'm not positive if the limitation of the partitioning applies to all phones with 2.2 or higher, though. I've read some threads for other phones that officially ran 2.2 in which they mention partitioning to be able to use old style Apps2SD instead of the native one, and there wasn't any mention of any complicated partitioning scheme.
Does anyone know enough off the top of their head to verify this?
I have a HTC Legend running on NewSense RC4. I have App2SD installed. I've changed the default install location to SD Card via " pm shell setInstallLocation 2". Though I've done all this, I have only around 2-3 MB space always. I're removed the data and cache for many apps. Yet, this is the situation. And I only have 52 APPS.
Please tell me another method to increase the amount of space. Please don't sugesst me to flash to another ROM.
I also read somewhere about partitions on SD card or something. Can you please enlighten me on this?
Note: I read to fast and COMPLETELY skipped the part where you said "Don't tell me to flash another rom" I am soooooo sorry!
The only other option I can give you is to flash Cyanogenmod7 and use data2ext if you want app space, but that is probably out of the question for you!
On the partitioning note:
Partitioning quite simply means splitting your microSD card into 2 or more PARTS (hintART-itioning). Often times, partitioning is used to create a separate space for apps2SD or data2ext. The simplest way to partition is to download rom manager (you must have root and be able to boot into recovery) and choose the option "partition sd card" choose 0 swap , then choose 512mb partitioning space! WARNING: this will delete EVERYTHING on your memory card, so either turn back, or backip tour mem. Card! After it is partitioned, you can proceed to add apps to the new partition of your SD card. Note this will, like I said, split your memory card space! Ex:
If you hav a 1 GB (1024 MB) Memory card, after partitioning, your memory for files will decrease to 512 mb, while 512 mb is reserved for your apps!
Just a word of advice from a fellow XDA-er!
I am not aware whether or not the HTC legend runs Cyanogenmod7 or not, but it would be well worth the flash to use it. Unless you are in love with the Sense UI (because CM7 uses 2.3.3 Gingerbread) then come on over to the Cyan side . Data2ext takes your ENTIRE data section of your phone (that part that holds the meat and bones of an app, PLUS the huge apk file) and puts it in that partition you created. Data2ext is simply a flashable script that puts that partition in action. After flashing the script via recovery, just go to your terminal emulator app on your phone and on the first line, type "su" (without quotes) and then type "data2ext --enable" (exactly as typed without quotes) and vuala, your REAL data section on your phone is literally virtually UNTOUCHED! Which makes your phone a lot faster. There is also a script that let's you choose the size of your partition (no more than 2 GB is strongly recommended) but I haven't used that script just yet, but will soon! Data2ext is WAY bettr than apps to SD! I know that I did way more than just answer your question, but I wanted to answer, plus give a better alternative should you choose to use it
Hope I answered ur question,
Ognimnella
Sent from my T-Mobile myTouch 3G Slide using XDA App
ognimnella said:
Note: I read to fast and COMPLETELY skipped the part where you said "Don't tell me to flash another rom" I am soooooo sorry!
The only other option I can give you is to flash Cyanogenmod7 and use data2ext if you want app space, but that is probably out of the question for you!
On the partitioning note:
Partitioning quite simply means splitting your microSD card into 2 or more PARTS (hintART-itioning). Often times, partitioning is used to create a separate space for apps2SD or data2ext. The simplest way to partition is to download rom manager (you must have root and be able to boot into recovery) and choose the option "partition sd card" choose 0 swap , then choose 512mb partitioning space! WARNING: this will delete EVERYTHING on your memory card, so either turn back, or backip tour mem. Card! After it is partitioned, you can proceed to add apps to the new partition of your SD card. Note this will, like I said, split your memory card space! Ex:
If you hav a 1 GB (1024 MB) Memory card, after partitioning, your memory for files will decrease to 512 mb, while 512 mb is reserved for your apps!
Just a word of advice from a fellow XDA-er!
I am not aware whether or not the HTC legend runs Cyanogenmod7 or not, but it would be well worth the flash to use it. Unless you are in love with the Sense UI (because CM7 uses 2.3.3 Gingerbread) then come on over to the Cyan side . Data2ext takes your ENTIRE data section of your phone (that part that holds the meat and bones of an app, PLUS the huge apk file) and puts it in that partition you created. Data2ext is simply a flashable script that puts that partition in action. After flashing the script via recovery, just go to your terminal emulator app on your phone and on the first line, type "su" (without quotes) and then type "data2ext --enable" (exactly as typed without quotes) and vuala, your REAL data section on your phone is literally virtually UNTOUCHED! Which makes your phone a lot faster. There is also a script that let's you choose the size of your partition (no more than 2 GB is strongly recommended) but I haven't used that script just yet, but will soon! Data2ext is WAY bettr than apps to SD! I know that I did way more than just answer your question, but I wanted to answer, plus give a better alternative should you choose to use it
Hope I answered ur question,
Ognimnella
Sent from my T-Mobile myTouch 3G Slide using XDA App
Click to expand...
Click to collapse
Yes, I read about the partitioning method. I've a few questions.
1. Will this method work on ANY ROM ?
2. Will I reclaim ALL my internal memory?
3. Is this is a sure shot method to install AS MANY apps as we need (the only condition being you that much SD card partition space) ?
4. Can you please link me to a detailed tutorial?
abhishek_turbo911 said:
Yes, I read about the partitioning method. I've a few questions.
1. Will this method work on ANY ROM ?
2. Will I reclaim ALL my internal memory?
3. Is this is a sure shot method to install AS MANY apps as we need (the only condition being you that much SD card partition space) ?
4. Can you please link me to a detailed tutorial?
Click to expand...
Click to collapse
1. Method will only work on rom that support it.
2. You will get a lot of internal memory back but data will remain internal unless you move app's data to sd-ext also.
3. Method trick the phone into thinking the sd-ext is part of your internal memory so you'll be able to install a good amount of apps.
4. Search Dark Tremor's a2sd or S2E in the market.
abhishek_turbo911 said:
Yes, I read about the partitioning method. I've a few questions.
1. Will this method work on ANY ROM ?
2. Will I reclaim ALL my internal memory?
3. Is this is a sure shot method to install AS MANY apps as we need (the only condition being you that much SD card partition space) ?
4. Can you please link me to a detailed tutorial?
Click to expand...
Click to collapse
1. No to my knowledge it only works on CM7 (and you said flashing a new rom is out of the question)
2. Yes, plus more
3. Yes, so far, I hav somewhere around 85 apps installed (and that's with 512 mb only, with 150-200mb still left
4. http://forum.xda-developers.com/showthread.php?t=902395
P.S. - If you want to have the freedom of installing up to 2GB partition space for apps, use data2ext-v4. If you want the already preset 512mb, then use data2ext-v7 (it is thoroughly explained in the post)
Sent from my T-Mobile myTouch 3G Slide using XDA App
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.
First of all i am not a dev, and the statements bellow are confirmed by devs and known guys from our O1 community like Maktail and Miasmic (thanks guys).
Most of us use a2sd scripts like darktremmor, ungaze, link2sd etc. and many of those are suppose to provide us with practically unlimited sd space for apps and data. But the common problem which allways occures is that after moving one too much apps to sd you will get at some point bootloops. The phone will not be able to load all apps from sdext partition and reboots all the time. So no a2sd script is able to provide what is ment for.
My question of why use a2sd script is related to the fact that moving apps to sd using built in android script which resides in every ROM (even stock obviously), moves to sd the same amount of apps as other scripts mentioned and has the same behaviour of bootlooping when too many apps are moved to sd. The only difference is that other scripts provide more options, like moving dalvikcache to sd. But that doesn`t help either.
So why use a2sd scripts when the result is the same as using stock android script?
A2sd dev dk_zero-cool (thanks) said here http://forum.xda-developers.com/showthread.php?t=1342387&page=25 that is common knoledge that android cannot handle more than 1GB external data and recommended to use no more than 1,5 GB sdext partition formated with other recovery than CWM which is buggy. Did that and results are the same bootloops. Which means that moving too many apps to sd gives at some point system instability no matter what app or which script we use.
That is why more exepensive phones have more internal mem, up to 16GB in nexus case for example, which is using internal mem even for data games storrage. In that case they use a script to link internal sd data to external sd data (folder mounting), which is of no use for us.
Using DT, ungaze and android built in move to sd option, i could move to sd the same amount of apps before getting bootloops. So why buther using all king of scripts when the resilt is the same?
And now i get to the real questions, which are:
Is there any a2sd script that gives the use of more than 1.5 GB of external data without system instability (bootloops)? (i could move about 1.2 GB to sdext using ungaze) Please post the answer to this after you tested and moved or linked to sd more than 1.5 GB of apps.
Is there a 1 or 1.5 GB limit of external data which android (Linux) can handle before getting instable? If so, can this limit be overcome?
If there is a limit, why the options to create more than 2 GB sdext partitions in recoveries?
Can some nice dev make a script that lets the phone give us a slap on the face when getting close to the point where the system gets instable, if the limit of external space cannot be overcome? It seems that most of a2sd script devs discontinued their work.
my opinion
I have used both ungaze and link2sd... link2sd got unstable when i am using almost over a gig of Ext partition while right now I'm using ungaze with 1.7gb of used Ext partition... It was stable for me... No bootloop or anything...
Using the latest cm7 nightly rom, fk v4...
EveryThing has it's own LIMITATION
amao10 said:
I have used both ungaze and link2sd... link2sd got unstable when i am using almost over a gig of Ext partition while right now I'm using ungaze with 1.7gb of used Ext partition... It was stable for me... No bootloop or anything...
Using the latest cm7 nightly rom, fk v4...
Click to expand...
Click to collapse
Really? 1.7 Gb and stable? Ext 4? Did you use CWM to make it? What card do you use?
New great a2sd mounting folders like disks! Need some testers here guys, please help. Maybe this way we can solve a2sd bootloops.
Must see this:
http://forum.xda-developers.com/showthread.php?t=1502893&page=6
based on my experience
Ext 2, used amonra 3.0.6, class 4 16gb transend, faster boot up than link2sd...
amao10 said:
Ext 2, used amonra 3.0.6, class 4 16gb transend, faster boot up than link2sd...
Click to expand...
Click to collapse
So nothing special. Close to what is use. Except for ext2. I use ext4. Could ext2 be more stable?
does anyone has proof that internal sd card is better & faster than eksternal sd card class 10?
Is there really need for a proof on that matter? The fact that class 10 is the latest technology doesn`t make it ultimate.
voyager20021 said:
Is there really need for a proof on that matter? The fact that class 10 is the latest technology doesn`t make it ultimate.
Click to expand...
Click to collapse
yes but it makes sense if your internal sd card is only class 2 (imagine factory want to cut budget product and add low sd card read & write).
one thing for sure, my quadrant says about 800 using internal sd card, and now about 2000 using eksternal. and if someone say that quadrant score is irrelevant, i only ask, why?
I use link2sd with 512 or 600-700 MB EXT3, and never got a problem, I prefer huge apps/games like NFS shift, in internal memory and data obviously in normal SD partition, and I prefer keeping apps like facebook, camera360 and other [unmoveable by default] apps in EXT3.. this way I can install several apps without any problem
I dont know if this has been asked before and I am feeling lazy to search. Does ungaze data2sd work with ext4 now?
i often have this problem: There is an app2sd-gui DT script included in the rom... and this automatically places apps to the fat partition on the sd card ..
now, i always partition my sdcards with a second ext4 partition and prefer to use that one as an sd-ext directory and use linking to place my apps and all the stuff on my sd.
This allows me to use virtually unlimited storage and keep my internal memory completely free... (i also have a htc wildfire with CM7 and this setup; there i have about 70 apps installed. the internal memory has about 10 MB in use with some files i really wanted to have there so they always start fast like go keyboard, go contacts ex and my ringtones / alarm sounds. All other files are on my 16 gb sd card)
With a lot of the roms i've been trying i just can't get this working on my galaxy ace... especially the ICS roms i can't see my EXT4 partition as /SD-EXT for some reason, but often it gets mounted as /System/SD and thus link2sd cannot use my second partition.
Especially if app2sd is builtin as a system app this seems to be a problem. Has anyone ideas on how i could get this working again with these roms?
BoGy1980 said:
i often have this problem: There is an app2sd-gui DT script included in the rom... and this automatically places apps to the fat partition on the sd card ..
now, i always partition my sdcards with a second ext4 partition and prefer to use that one as an sd-ext directory and use linking to place my apps and all the stuff on my sd.
This allows me to use virtually unlimited storage and keep my internal memory completely free... (i also have a htc wildfire with CM7 and this setup; there i have about 70 apps installed. the internal memory has about 10 MB in use with some files i really wanted to have there so they always start fast like go keyboard, go contacts ex and my ringtones / alarm sounds. All other files are on my 16 gb sd card)
With a lot of the roms i've been trying i just can't get this working on my galaxy ace... especially the ICS roms i can't see my EXT4 partition as /SD-EXT for some reason, but often it gets mounted as /System/SD and thus link2sd cannot use my second partition.
Especially if app2sd is builtin as a system app this seems to be a problem. Has anyone ideas on how i could get this working again with these roms?
Click to expand...
Click to collapse
You have to edit the a2sd-script wich should be located in /etc/init.d/
But using "Link2sd" would be much easier. It is a well structured app and the usage is simple, because the first time (when you open the app) you have to choose your partition and the mountscript will be created automatically.
You can get Link2SD from this xda-thread or the play store
BoGy1980 said:
i often have this problem: There is an app2sd-gui DT script included in the rom... and this automatically places apps to the fat partition on the sd card ..
now, i always partition my sdcards with a second ext4 partition and prefer to use that one as an sd-ext directory and use linking to place my apps and all the stuff on my sd.
This allows me to use virtually unlimited storage and keep my internal memory completely free... (i also have a htc wildfire with CM7 and this setup; there i have about 70 apps installed. the internal memory has about 10 MB in use with some files i really wanted to have there so they always start fast like go keyboard, go contacts ex and my ringtones / alarm sounds. All other files are on my 16 gb sd card)
With a lot of the roms i've been trying i just can't get this working on my galaxy ace... especially the ICS roms i can't see my EXT4 partition as /SD-EXT for some reason, but often it gets mounted as /System/SD and thus link2sd cannot use my second partition.
Especially if app2sd is builtin as a system app this seems to be a problem. Has anyone ideas on how i could get this working again with these roms?
Click to expand...
Click to collapse
sd-ext is for CYANOGENMOd only...in stock based rom's u wont find a sd-ext..so s2e wont work.... but charmingly link2sd works....
now if it isn't working what shall u do???
-- if it says mount script not created,, partiotion is busy,,,, reflash the rom or i tried flashing another rom on wich link2sd worked and then reflashing the rom u want... install link2sd apk.. choose ext4 partition reboot.... (it works u can switch from cm7 to stock it wont be a problem)
- if ur sd-ext partition is of ext3 type,,, still choose ext4 on link2sd partition type screen
Fly-High said:
You have to edit the a2sd-script wich should be located in /etc/init.d/
But using "Link2sd" would be much easier. It is a well structured app and the usage is simple, because the first time (when you open the app) you have to choose your partition and the mountscript will be created automatically.
Click to expand...
Click to collapse
I always try to use links2sd; but if app2sd(gui) is installed it won't work.
I'd like to edit the init.d 'mount' script, but i don't know how to open thiis since it always says it cannot be found when i try to open it for editing or even for reading.
(i'm trying to open it with an app that has SU rights like Total Commander)
i have some experience with android and installing custom roms ; but i don't have real experience with editing files in a live OS.
Or should i edit the files in the APK before installing it? (isn't this going to break the APK's CRC-key rendering the file unusableN)
I already thank you guys for reading and sharing your knowledge...
I found it
I could edit the mountsd file in the original ZIP (which is not a crc'ed APK )
then reflash my device.
I removed everything in the mountsd file except this;
Code:
#!/system/bin/sh
#
# mount ext partition from sd card
(so this is what's left)
then i installed S2E & Link2SD, i let link2sd initialize it's scripts and pataboom; i got access again after the next reboot of my device ... finally i have a galaxy ace with unlimited space (or at least kinda limitless compared to the 120mb you get)
i was so used to the big space since it worked like a shine on my htc wildfire (like 60+ apps and only a few mb in use by some apps i really wanted on the internal memory so they start up fast anytime (no interference when other apps are running/starting).
I really love link2sd since it allows you to put apps on external memory and still use the widgets/services/.... while app2sd can't do that
thx again for your help guys! (although i did a lot of fo the job myself too