Related
Hi,
I'm getting low on space message on my hero running VillainRom 6.1. Tried rebooting, still there. I've only tried to install one or 2 apps with the message there, so not sure if thats actually been affected.
settings-->sdcard & phone storage-->internal storage shows 14.83mb
quick system info shows:
sd card storage free 2.14gb
a2sd storage 249mb free (total 457mb)
system cache 129mb free
memory 37.35mb free
there doesn't seem to be any more processes running than usual - only around 3-4.
I do have quite a lot of apps, over 100, probably closer to 200, I havent counted.
btw thanks to everyone on this site, I'm new to flashing roms but having fun learning, and my phones definitely got a new lease of life.
use the apps2sd checker to make sure its working. If it is id say increase your partition from 512 to more
Just because the app is installed on the sd card (assuming its working properly) doesn't mean the davilk cache for the app has moved. unless you move this as well (which isn't really recommended) each time you install an app system memory will still go down a little.
Lennyuk said:
Just because the app is installed on the sd card (assuming its working properly) doesn't mean the davilk cache for the app has moved. unless you move this as well (which isn't really recommended) each time you install an app system memory will still go down a little.
Click to expand...
Click to collapse
http://4943922026776299669-a-180274...lcSrZUn2-7KkHiRo-ew0R2SEebAQ==&attredirects=0
u need this which is an update. copy this file into the root of the memory card and through the recovery image install it from "zip file from sdcard"
after that restart the phone and check your memory is should be 120mb
Indy_Hero said:
use the apps2sd checker to make sure its working. If it is id say increase your partition from 512 to more
Click to expand...
Click to collapse
thanks for the suggestion
a2sd check script says its working fine, also checked via adb shell.
This is what I then did to the partition size:
I copied SD card contents (both partitions) into ubuntu.
then I put SD back into phone and repartitioned using 1gb for ext2
then I copied back SD card contents from ubuntu.
I assumed this would work, but when I booted I was getting FC all the time. Bart backup sorted it out but I am still left wondering why this method of increasing partition size didnt work??
In any case quick system info shows a2sd has more space, but still got low space message.
qasi said:
...
u need this which is an update. copy this file into the root of the memory card and through the recovery image install it from "zip file from sdcard"
after that restart the phone and check your memory is should be 120mb
Click to expand...
Click to collapse
seems to have solved the problem!! thanks alot mate.
would you by any chance out of interest know why copying ext2 contents from sdcard as outlined above didnt work? - may have some future relevance if changing/upgrading roms.
Thanks again
neuro_99 said:
thanks for the suggestion
a2sd check script says its working fine, also checked via adb shell.
This is what I then did to the partition size:
I copied SD card contents (both partitions) into ubuntu.
then I put SD back into phone and repartitioned using 1gb for ext2
then I copied back SD card contents from ubuntu.
I assumed this would work, but when I booted I was getting FC all the time. Bart backup sorted it out but I am still left wondering why this method of increasing partition size didnt work??
In any case quick system info shows a2sd has more space, but still got low space message.
seems to have solved the problem!! thanks alot mate.
would you by any chance out of interest know why copying ext2 contents from sdcard as outlined above didnt work? - may have some future relevance if changing/upgrading roms.
Thanks again
Click to expand...
Click to collapse
this is because the ramon recovery image had been linked with ext2 with a 512mb partition and u selected 1gb. im not quite sure about that.
chnagin rom is quite simple beucase you have to is
1.backup using nandroid
2.make sure you wipe everything. (also battery and rotating settings)
3. Re partition your sdcard to hold 1 ext2 partition and last partition should be the rest in fat32
4. Flash the rom you want through "zip file from sd card"
5. Reboot.
im a newb so i dont have much knowledge but patching up problems that i had, so that i can help others.
it can be pain especailly rooting!!!
So thats how you would flash a rom, but what if you wanted to keep your a2sd apps? So you dont have to install them all over again in the new rom when you wiped everything.
I think I read somewhere that it should be possible to leave the contents of ext2 as it is, and that should carry forward to the next rom, but I havent been able to test it myself yet.
I installed the magnificent Cronos 0.0.9 ROM (Android 2.3 Gingerbread) in my HTC Hero, following dkelley's instructions on the Developer forum for that device. It works brilliantly, speed is superb, and it looks like battery life is going to be better than the Cyanogen 6.1 it replaced.
Everything works for me : Camera, compass, GPS (sort of), auto brightness.
But there is one unusual problem. I cannot find any other forum threads that refer to this. When I use menu->Settings->Applications->Manage Applications, I can move apps to or from the SD card. Except it doesn't work most of the time. I get this message: "Failed to move application. There is not enough storage left"
I have 24MB free on the phone and 2.4GB free on the SD card. So it should not have a problem when I try to move anything (all but 2 of my apps are under 7MB). I have seen a case of being successful with an app of 730K moving to SD. But when I remove that, and try again with a 410K app, it fails. 90% of apps I have tried have failed.
I was very successful with this in my previous ROM, so I know it's not read errors on the SD.
I did forget to delete the old apps dot directory on the SD card before the upgrade. I don't know if that can cause a problem.
As I am too shiny and new, I can't post on the developer forum. A good rule, if it keeps the noise level slightly lower.
So I thought I would post here & see if anyone knows of general fixes for app 2 SD problems of this kind. Maybe it's just that the ROM is too Beta & it's to be expected. That's what happens out at the ragged edge
If u don't have an ext partition on your sdcard then I'm afraid it won't work on Cronos GB 0.0.9 Beta because the apps moved to External are moved on the fat partition and they Force Close all the time anyway on this rom. Now ... app2sd works verry weird on this rom. If u have an ext partition on your sdcard and if u want your apps to be on that partition (and they wont FC on you) all you need to do is let them on Internal (move to phone) and not External (move to sdcard). The apps are installed/moved to the ext partition instead and not on the phone's actual memory (again... as I said weird but it works). If u want to be able to move the apps to sdcard .. I recomend you back-up your files from sdcard to your pc, go to recovery and make an ext partition and wipe it(just in case) and boot your phone and try installing your apps.I'm installing my apps automaticaly to the ext partition by choosing the Install Location to Internal from CM Extra->Application settings. Sorry I wrote alot and if I haven't made myself clear but I'm still at work (3rd shift) and I am tired.
Example: I have a 2gb sdcard... On it I have the ext partition of 240MB, the rest is the fat partition.If I leave my apps on Internal(move to phone), my Phone's Memory is 140/173MB and my ext partition 47.5/240MB .. If I move them to External(move to sd card), My Phone's Memory is 140/173 and my ext partition is about 230/240 MB because the apps are moved to the fat partition (with your errors) and they Force Close when launched on this rom.
You're right, I can see that in the release notes. I am surprised, it's a long time since I have used a ROM that supported ext partitions. Most of them seem to use the Google apps2SD method now.
Cyanogen has even stated that it is no longer officially supported by them.
So I guess it's just individual developers who still prefer the ext approach that still use it.
It's not too hard to do...
Thanks for the tip
You're welcome! Remember that your sdcard content will be deleted when you will partition your sdcard so make a backup if you need them. I find ext is better than normal because you can use the apps from your sdcard while you phone is connected to the computer (your PC mounts the fat partition and leaves the ext partition to be used as normal on the phone and I find that a good thing)
Has anyone got this working? I used to have Link2SD in 2.1 but now the ext partition is the only partition recognized by GB and not my main partition. I can access my main partition from USB connect, but not from within the phone. Anyone has the same issue?
You can natively move apps to the SD on GB in Options>Applications>Manage applications. Choose an app that supports it and the option to move to sd will be there. No partition needed.
Thx, i will just fix up my SD card into a single partition again then
Does this also mean that I don't need the app Apps2SD anymore?
With App2SD you can quickly indicate which apps can be moved to SD. So I still have it there. Furthermore, App2SD also quickly clean your cache.
Link2SD gave the option of moving ANY app to the ext2 partition. The native gingerbread app2sd doesn't support moving all apps to the SD card.
Any way of making link2sd work on GB 2.3.3?
can anyone confirm what's the current sdcard partition layout. also which partition is detected in phone.
i think i have an idea which might help up getting this to work.
anantshri said:
can anyone confirm what's the current sdcard partition layout. also which partition is detected in phone.
i think i have an idea which might help up getting this to work.
Click to expand...
Click to collapse
@Anant: My SD is setup as per the guidelines described here:
http://forum.xda-developers.com/showpost.php?p=10711328&postcount=1
I have a 8GB card and I have allocated 7.05 GB of FAT32 memory to the Data partition, and have allocated 0.5GB to the secondary partition. This partition was also setup as FAT32 since i had issues with EXT2.
*Edit: After the 2.3.3 update, the X10 now detects only the 2nd partition (480MB) instead of the data partition (7GB) - but when I plug into a PC, the data partition gets mounted correctly.
Hope that helped.
That is not good, it means that you cannot transfer data or programs between your PC and the 7GB partition... is there a way to fix this?
When you plug into pc, your data-partition mounts correctly, so you can copy your data to your pc as a backup.
I recommend using a adapter to connect the sd-card to your pc, formatting both partitions, and then put it back. I did it that way, be it that I removed my second partition and went back to one partition only, 8 Gb, and all works fine now.
I don't intend to use Link2SD anymore, because in 2.3.3 the system can apply data2sd itself, I learned, with or without Apps2SD.
Good luck, greetz,
kwarkje
From my observation, the 2.3.3 android system moves the appdata to the sdcard only in certain large apps (apps >7mb in size?) which is good if you have are dealing with huge apks like AngryBirds, but not too handy if you have a huge number of small apps all ~3MB in size.
BTW the native app2sd isn't compatible with all apps.
Use "Move2SD Enabler" from Market to allow moving any app to SD.
https://market.android.com/details?id=com.leinardi.setinstalllocation&hl=en
This didnt work with my 32GB SD card... it is now a single 32GB FAT32 partition. What type of format should I use? FAT? EXT2?
kwarkje said:
When you plug into pc, your data-partition mounts correctly, so you can copy your data to your pc as a backup.
I recommend using a adapter to connect the sd-card to your pc, formatting both partitions, and then put it back. I did it that way, be it that I removed my second partition and went back to one partition only, 8 Gb, and all works fine now.
I don't intend to use Link2SD anymore, because in 2.3.3 the system can apply data2sd itself, I learned, with or without Apps2SD.
Good luck, greetz,
kwarkje
Click to expand...
Click to collapse
@doomed151:
Thats what I was looking for! Good find!
This app has its own hitch though: the move2sd enabler needs lots of caution...some apps aren't supported, and moving them to the SD causes them to crash. There is no way of knowing which apps can be moved and which ones can't. I happened to move GT Racing HD to the SD and it stopped working. Had to reinstall!
anantshri said:
can anyone confirm what's the current sdcard partition layout. also which partition is detected in phone.
i think i have an idea which might help up getting this to work.
Click to expand...
Click to collapse
@Anatshri Any luck on this? I would prefer to use link2sd instead of the native move2sd in GB.
I tried a 16gb & a 4gb sd card but couldn't get it to work. I've also tried ext2, ext3 & ext4 as the 2nd partition but I don't think the stock kernel supports any of them. The sd becomes unreadable after a reboot but if I connect directly to the pc I can see both partitions.
If I make both fat32 partitions only the 2nd partition gets mounted. Do you think this is kernel related as well or can we modify the mounting scripts to correct this?
I am suffering from bad health conditions right now so can't work much however all I can see right now is if this is the case you can do two things
1) create a script that mounts partition 1 at /data/sd-ext coz link2 sd needs mounted partition at this location. I suppose init.d script could help us. However
2) the problem would be that recovery will detect only partiton one
Sent from my X10i using XDA App
anantshri said:
I am suffering from bad health conditions right now so can't work much however all I can see right now is if this is the case you can do two things
1) create a script that mounts partition 1 at /data/sd-ext coz link2 sd needs mounted partition at this location. I suppose init.d script could help us. However
2) the problem would be that recovery will detect only partiton one
Sent from my X10i using XDA App
Click to expand...
Click to collapse
I'm sorry to hear about your health, hopefully it's nothing serious and you get well soon. Thanks for the suggestion, I'll give this a try when I get a chance.
Any solution on this?
I move from 2.2 to 2.3.4 and link2sd don't work anymore cannot mount the 2nd fat32 partition.
App2SD sucks because doesnt allow some apps to get moved.
Thanks
Lockon Stratos said:
I'm sorry to hear about your health, hopefully it's nothing serious and you get well soon. Thanks for the suggestion, I'll give this a try when I get a chance.
Click to expand...
Click to collapse
Thanks for the wishes.
I have extended weekend this time will try to give my old card a twist and see if i can get link2sd work again on my handset.
bbsrailfan said:
Link2SD gave the option of moving ANY app to the ext2 partition. The native gingerbread app2sd doesn't support moving all apps to the SD card.
Any way of making link2sd work on GB 2.3.3?
Click to expand...
Click to collapse
I agree with you and hope that we will have this possibility, I really miss link2sd, the best app ever to move apps to sd.
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 looked on forum for some summary what is general use of SD-ext partition.
So far I found some explanations and some solutions for CM ROMs.
So, if I uderstand correctly, I can use sd-ext
- either as seamless extension of internal partitions (/data, /system, /cache), for more storage
- and/or for installing apps on SD card, that work when SD card is connected to PC ass mass storage
Is it right?
I am on AOKP ROM, I tried to use it for moving apps with Link2SD and Android Assistent, but they tried to move apps to sdcard.
So, what is correct use of sd-ext and how to make it with AOKP? Mainly I want to extend internal storage (384MB)
I think you need to have a ext3 partition in the SD...
try this method...
MrTapa said:
Ok so I am gonna make an easy guide. But befor i start i will say the requirements
Requirements
1.Rooted
2.Busybox installed(v19.4 reccomended)
4.Card reader
So here we are.
1.Download MiniTool Partition
2.Remove the sd-card from phone and put it in a card reader and plug in pc.
4.Select only important files like Pictures, Music , Titanium and clockworkmod backups and all that important stuff for you
5.Copy them to a folder in computer.
6.Install MiniToolPartition and open it.
7.You will see your hard drives and your sd card.
8. Right click on sd card and click delete. Then again right click and Create.
9.Select "File System:" FAT when you have 2GB or smaller card.
Select "File System:" FAT32 when you have 4GB or greater card.
10.Dont select the whole volume. Select for example if you have 4GB card select 3GB if you want your sd-ext to be 1GB
11.When you are done.Again right click on the sd card and create ext2 or ext3 partition.Then select the full volume allwoed.
12.Make sure that this volume is enough for all apps on your phone.
13.Whn you are done click on the apply button on the top left corner. Wait for it to finish. When you are done. Copy teh prevously backed up data to the card.
14.Put it on the phone and on the market download Link2SD
15.Run the app and it will ask for root.Then select your tipe of partition. tehn reboot.
16.After reboot go to the app and you can mult iselect your apps with the options menu. Then in actions.Click Create link. Then ok.
17.You are done. Now you have a cleaner sd and initial storage
FAQ:
Q:What is sd-ext partition.
A: Its a tipe of partiton than linux supports so Android can use it as an initial memory.
Q:Why i dont see more space when i go to Apps in phones settings
A:The phone cant display sd-ext partiton. you can view it via Link2SD.(Otions>Storage info)
Alternetive version of discribing:http://forum.xda-developers.com/showthread.php?t=1338708
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=1750888
thanks!
I used MiniTool Partition Wizard but Neo couldn't find it.
Luckily I found this http://www.butonic.de/2012/03/14/partitioning-the-sd-card-for-app2ext-with-adb-shell/ and was able to fdisk my sdcard from putty connected to sshdroid. Now SD is correctly formatted and Link2SD created mount script.
I can't tell if it works or no. From what I expect, there should be more MB when I look at Settings -> Storage, because Link2SD extends my internal storage... but there is still the same ~420MB.
Can it be that Link2SD silently moves new apps to /sd-ext, but internal storage is still the same?
DarshanaXN said:
I think you need to have a ext3 partition in the SD...
try this method...
http://forum.xda-developers.com/showthread.php?t=1750888
Click to expand...
Click to collapse
PetrGasparik said:
thanks!
I can't tell if it works or no. From what I expect, there should be more MB when I look at Settings -> Storage, because Link2SD extends my internal storage... but there is still the same ~420MB.
Can it be that Link2SD silently moves new apps to /sd-ext, but internal storage is still the same?
Click to expand...
Click to collapse
I think you missed this line in my post.
Q:Why i dont see more space when i go to Apps
in phones settings
A:The phone cant display sd-ext partiton. you
can view it via Link2SD.(Otions>Storage info)
although phone settings doesn't display about sd-ext you may see that amount of free storage increases as you create links with link2sd. I've attached two screenshots showing one before linking asphalt and anti terror shooter to sd-ext and after linking.
I had the same problem with minitool. then I used CWM to partition the sd.
u need to format ur SD to ext2 and you need link2sd app
indycar said:
u need to format ur SD to ext2 and you need link2sd app
Click to expand...
Click to collapse
It depends on the kernel which file format it supports.
The FAQs from link2sd says that fat 32 is supported by every Android / kernel for SD ext partition.
This is my still unused SD ext fat 32 partition.
So if you are not sure fat 32 should always do the work. By the way mini partition tool works great.
Send from my Neo V with JJHybrid 3.3b and Night Elf 1.4 using Tapatalk 2
use ext 2
ext3 and 4 didnt work on my neo
Hi,
I used Link2SD for some time. I had some troubles with ROM - random reboots, YT not working etc
I stopped using Link2SD, because I tried to eliminate everything "unnatural".
At the end, I changed ROM from AOKP to Paranoid and it solved all these troubles (there are some new ones )
Now, then I installed Link2SD and try to create mount script, Link2SD fails with "Mounting script cannot be created"
what do you suggest? reformat card partition? I would like to re-link apps that are there.
DarshanaXN said:
I think you missed this line in my post.
Q:Why i dont see more space when i go to Apps
in phones settings
A:The phone cant display sd-ext partiton. you
can view it via Link2SD.(Otions>Storage info)
although phone settings doesn't display about sd-ext you may see that amount of free storage increases as you create links with link2sd. I've attached two screenshots showing one before linking asphalt and anti terror shooter to sd-ext and after linking.
I had the same problem with minitool. then I used CWM to partition the sd.
Click to expand...
Click to collapse
Yeah, you're right. It is still a little of mystery for me, but hey, I learn to use it
Anyway, Minitool IS great, but when I formatted a card with it, phone couldn't read it. So I had to use ssh to phone.