What is the process for disabling apps2sd in CM. I have no need for it on the mytouch, but I still want to use compcache which requires the ext partition
Look in the a2sd.sh script in /system/bin. You'll have to remove some things that link the /data/app and app-private to /system/sd
Here's a modified a2sd. Just stick it in /system/bin and you're good to go.
I use this on my CM installation with no issues
Also I would think that you would have to edit your userinit.sh to point to /dev/block/mmcblk0p2 instead of /dev/block/mmcblk0p3. I think if you remove anything associating apps to sd in the a2sd script it shouldn't activate it, but if you leave the call to the userinit.sh it will still work on each boot. Or you could nandroid, then just remove the a2sd script, and manually activate the userinit.sh, just an idea
david1171 said:
Also I would think that you would have to edit your userinit.sh to point to /dev/block/mmcblk0p2 instead of /dev/block/mmcblk0p3. I think if you remove anything associating apps to sd in the a2sd script it shouldn't activate it, but if you leave the call to the userinit.sh it will still work on each boot. Or you could nandroid, then just remove the a2sd script, and manually activate the userinit.sh, just an idea
Click to expand...
Click to collapse
Problem is to activate compcache with back_swapping you of course have to change your userinit for that, but also disable a2sd as that will run auto if it detects an ext partition(that and the swap partition are required for compcache with backswaping)
not if you were to change the a2sd script, say you made it look at /dev/block/mmcblk0p4, you have no 4th partition therefore, in theory, apps2sd would not be activated and you could still use a2sd to call your modified userinit.sh which would point to /dev/block/mmcblk0p2 which would be your linux-swap partition since you have no need for the ext2 partition. all this is just theory though
here is a modified a2sd script that points to dev/block/mmcblk0p4 since it is non-existent and a modified userinit.sh and a modified user.conf that both point to dev/block/mmcblk0p2. see if these work. i know you know how to use adb wes so i shouldn't have to give you the commands lol.
Well then it would be just as simple to comment out the activation of apps2sd like obsidianx did, david I know right lol
not seeing a2sd.sh or apps2sd in /system/sd on CM 4.2.3.1
ObsidianX said:
Here's a modified a2sd. Just stick it in /system/bin and you're good to go.
I use this on my CM installation with no issues
Click to expand...
Click to collapse
So how do do this? I completely understand the user.conf and userinit.sh and how they go in /system/sd/ chmod'd 755 but do I just copy the a2sd file to /system/bin despite the fact there isn't an a2sd.sh file there already?
Also I'm sure I can use du somehow to tell if I've used too much space on my ext since enabling it (I've installed a few programs since partitioning and installing CM). What would that be or am I screwed now that I did install something?
Related
I have partitioned sd card and I have the hello im apk on the sd and I want it on my phone because it wont let me change my buddy pic it says please make sure your sd card is in the phone so Im going to try to put it back on internal storage to see if it works. So how do I move it? I parted with apps2sd but the app wont work with cyan 4.0.1 so how Do I move it?
Apps2sd is really an all or nothing proposition. You can't have one app on internal memory and the rest on the SD card.
If you want to get rid of apps2sd altogether I can tell you how to move everything back.
OTOH, if an app is complaining about the sd card it's probably talking about the fat32 partition that it wants to store images on. Is your fat32 close to being full or something?
on a side note im on cyan 4.0.1 I was at 3.6.8.1 when I used the apps2d app and now when I try to open it it says Oops! Looks like you need to go through the tutorial to set up apps to sd. Please go to blah blah blah why is it doing this
what do I have to do to get this app running gain I already haves apps going to sd.
The top part of Cyanogen's stable thread says not to use any other method of apps to sd because his has a script built in.
So. Stop fiddling with whatever apps2sd app you have.
go to terminal and type:
Code:
su
ls /dev/block/mm*
Tell me what you see. (And please take a moment to make your posts a little more readable, I'm having a hard time deciphering what you're asking/saying. )
what Am I suppost to do? I dont want to do it without knowing
open the application 'terminal emulator' -- this is like the dos 'command prompt' in windows or a term window in Linux
type 'su' and press enter -- this Switches User to root, or the administrator of the machine (your phone)
type 'ls /dev/block/mm*' -- 'ls' is 'list' directories. /dev is where all the devices are, block is hard-drive like devices (your internal memory and the sd card) and mm* is every block device that starts with 'mm....' which should be mmcblk0 (the sdcard), mmcblk0p1 (the fat32 partition) and mmcblk0p2 (the ext partition)
If the last exists, the cyanogen automatic apps2sd will have already moved all your applications there. If only one exists, it means you either formatted the whole SD card to ext2 for apps2sd (and left nothing fat32) or formatted none of it and your apps are already on your phone.
if your 'ls /dev/block/mm*' says that you have a mmcblk0p2, than run "ls /system/sd/app/*" and you should see a bunch of files ending in .apk. If so, then you have to undo apps2sd to get the Hello IM app back to internal memory.
Report back on the outputs of the above and further instructions will be provided.
Ok Iv done all that so how do I undo them and if so how will I get them back?
Tell me what all that said back when you typed it in. THEN I can tell you what to do.
I see all my apk files now what? I want to move that 1 app onto the phone memory and every other apk on the sd. Im ready for the next step.
I see a bunch of files ending in .apk now what?
Hmm. I just looked up 'Hello IM!' and see that it's a paid app.
So, we can move just paid apps to the internal memory and leave the free ones on the sd card.
if yes run the following in terminal emulator:
su
rm /data/app-private
mkdir /data/app-private
cp /system/sd/app-private/* /data/app-private
Copying the apps may not work and you may have to uninstall/reinstall, but when you install them they'll be on the internal memory.
Oh, but cyanogenmod will put them back on the sd card when you reboot, so if having the app on the internal memory does fix the problem, you'll have to edit the a2sd script.
The problem isn't that your apps are on the sdcard. The app itself doesn't know. Your partions may be out of whack or the app itself may just need to be reinstalled.
When your apps are on the sdcard they are on a different partition then what every app uses your sdcard for. Not sure if I wrote that where you can comprehend it or not...
wat do u mean out of wack
PsychoI3oy said:
If you want to get rid of apps2sd altogether I can tell you how to move everything back.
Click to expand...
Click to collapse
I've done some searching, and haven't found any way to do this that has worked for me. Could you please pass some of this info along?
Thanks.
HowTo - un-apps2sd (on CyanogenMod)
Ok, this is based on the assumption that you are running a Cyanogen rom. I'm sure it could be adopted for use on another one, but Cyanogen 4.0.x is what I'm running. You'll probably have to re-install any paid apps (app-private) but normal apps should run fine after this.
Instructions for use with adb:
Code:
adb remount
adb push a2sd.txt /system/bin/a2sd
adb shell
# rm /data/app
# mkdir /data/app
# cp /system/sd/app/* /data/app/
# rm /data/app-private
# mkdir /data/app-private
# cp -r /system/sd/app-private/* /data/app-private
# reboot
for terminal emulator, assuming the new a2sd.txt is on your sdcard:
Code:
mount -o rw,remount /system
mount -o rw,remount /data
cp /sdcard/a2sd.txt /system/bin/a2sd
and then continue the adb instructions from after 'adb shell'
after reboot you can confirm that it worked by running:
ls -l /system
from terminal emulator (no need to remount/su) and you should see 'app' and 'app-private' as directories (and not app -> /system/sd/app).
If you're running some other a2sd method, you'll have to edit/remove the script that's doing the linking, then delete the symlinks and copy back (should be similar to above).
The modified a2sd.txt attached just takes away the apps-to-sd part. Dalvik-cache is still run from /system/sd/ as are whatever other magical juicy bits he's got in there.
If you upgrade to another Cyanogen rom, the new version of a2sd will get pushed and everything will be moved back. The only way to get rid of it permanently would be to delete the ext2/3/4 partition on your sd card.
If you decide you want apps2sd again and don't want to upgrade, just put the a2sd.orig.txt back as /system/bin/a2sd and reboot, it'll automagically move everything back to the /system/sd/app on your ext partition.
I just did the un-apps2sd then put the original back and everything's fine (and was fine with un-apps2sd).
That should cover most things....
Thank you so much for the step by step instructions.
One minor correction, maybe, shouldn't there be a '/' at the end of the second to last line?
Also, for me I didn't copy over the modified a2sd.txt file. After I copied everything to internal I shutdown the phone and deleted the ext partition. All seems to be working well!
Thanks again.
daveerickson said:
Thank you so much for the step by step instructions.
One minor correction, maybe, shouldn't there be a '/' at the end of the second to last line?
Also, for me I didn't copy over the modified a2sd.txt file. After I copied everything to internal I shutdown the phone and deleted the ext partition. All seems to be working well!
Thanks again.
Click to expand...
Click to collapse
Trailing slashes are optional in most shells, including this one.
Glad it worked for you.
these doesn't seem to be working for 4.2.1, no a2sd file exists in /system/bin, maybe he moved it somewhere else, i'm trying to find it but i'm not being lucky.
any help?
No, he broke up the bits that were in a2sd and spread them across several files in /system/etc/init.d/
http://wiki.cyanogenmod.com/index.php/Removing_Apps2SD has the instructions now.
hey guys, i would just like to make sure that my settings are correct. i have a 32mb linux-swap partition.
im running cyanogen ROM and my swap place (on swapper) is /sdcard/swapfile.swp
Under advanced preferences, i checked the option of "Use Swap Partition" with the swap partition of dev/block/mmcblkop3
i always get a swapfile.swp in my fat32 partition.
thanks
Pretty sure linux-swap is automatic with the cyanogen's...
Nah, compcache is automatic on all new cm roms, but I found that it causes me the coma issuse on wake with it so I just use swap for it instead
ok im confused. so swapper and compcache do the same job? if so, then ill just uninstall swapper
rpesigan6 said:
ok im confused. so swapper and compcache do the same job? if so, then ill just uninstall swapper
Click to expand...
Click to collapse
If compcache is automatic, and you want to use linux-swap, you need to extract the user.conf from /system/bin, change the settings (the instructions are in there), and then push it back over. But if you're already satisfied with the performance, leave the tweaking to those who are more knowledgeable.
yeah im satisfied with the performance. ok i just uninstalled swapper. so about compcache.... correct me if im wrong, but my cache is currently being stored into my internal memory. i believe this is so cause i would always have to go to manage applications to clear cache
compcache has nothing to do with your caches. Compcache is a set of modules that compresses paged data to allow you to "extend' the available memory. goto google, apply fu.
hello all first post and hopefully last post... I have tried to search and search and read and read but still confused on some things. I just have a few questions the confusion comes from instructions how to do things but no reason or explanation why. so anyways here goes I started with no knowledge of any of this so I dont need help with root, and flashing roms or installing and using adb... I have a G1 with pvt board I also plan on using just the linux-swap for now not the compcache one so here goes
1) what is the difference in partitions (ext2 ext3) what is each needed or used for? like your main fat32 is for storing apps and data? one is a ram swap kinda like virtual memory? I just not sure if I would need ext 2 or ext3 or both...I am using hero roms... does the linux-swap partition count as a ext2 or 3? and lastly why do u need to convert a ext2 to and ext3 you cant just create an ext3 off the bat?
2) how do I know if the rom does not say what type of swap it is using as in comp or linux swap? I have read about the user.cfg file but kinda unclear in that... do I have to edit it or just check it from the zip file and see the settings? if so I see downloads for a user.cfg (of course prolly not the settings I need for that rom) but I just edit it and throw it on fat32 partition and it should work automatically? if the rom has compcache working can I still disable it and just use a linux-swap and just change the size of the swap?
3) what is the difference between the user.cfg and userinit.sh?
4) after the rom is flashed (my update.zip) it is ok to delete it off the sdcard?
5) so lastly if I want to put pics / music / videos do I just throw them on the fat32 partition but in what folder so it recognizes it? or do I need to download some kind of file manager to get into the flashed rom so I can see the correct media / download / camera folders and place them there? if I have to go the latter route do I need to do the whole adb "push" thing to get them in there? reason why I ask is with a normal G1 when you connect it with the data cable to your computer i can just see the folders but when rooted and flashed obvioulsy there is nothing to see
6)apps2sd runs and saves on what partition?
please dont kill me I honestly did search and read all over just seems confusing most of the "guides" tell me how to do things but I dont know why those things are usefull or needed to be done
Devious12345 said:
hello all first post and hopefully last post... I have tried to search and search and read and read but still confused on some things. I just have a few questions the confusion comes from instructions how to do things but no reason or explanation why. so anyways here goes I started with no knowledge of any of this so I dont need help with root, and flashing roms or installing and using adb... I have a G1 with pvt board I also plan on using just the linux-swap for now not the compcache one so here goes
1) what is the difference in partitions (ext2 ext3) what is each needed or used for? like your main fat32 is for storing apps and data? one is a ram swap kinda like virtual memory? I just not sure if I would need ext 2 or ext3 or both...I am using hero roms... does the linux-swap partition count as a ext2 or 3? and lastly why do u need to convert a ext2 to and ext3 you cant just create an ext3 off the bat?
2) how do I know if the rom does not say what type of swap it is using as in comp or linux swap? I have read about the user.cfg file but kinda unclear in that... do I have to edit it or just check it from the zip file and see the settings? if so I see downloads for a user.cfg (of course prolly not the settings I need for that rom) but I just edit it and throw it on fat32 partition and it should work automatically? if the rom has compcache working can I still disable it and just use a linux-swap and just change the size of the swap?
3) what is the difference between the user.cfg and userinit.sh?
4) after the rom is flashed (my update.zip) it is ok to delete it off the sdcard?
5) so lastly if I want to put pics / music / videos do I just throw them on the fat32 partition but in what folder so it recognizes it? or do I need to download some kind of file manager to get into the flashed rom so I can see the correct media / download / camera folders and place them there? if I have to go the latter route do I need to do the whole adb "push" thing to get them in there? reason why I ask is with a normal G1 when you connect it with the data cable to your computer i can just see the folders but when rooted and flashed obvioulsy there is nothing to see
6)apps2sd runs and saves on what partition?
please dont kill me I honestly did search and read all over just seems confusing most of the "guides" tell me how to do things but I dont know why those things are usefull or needed to be done
Click to expand...
Click to collapse
ill answer the 4th question coz im a lazy dawg,
and the answer is.......... YES!
Devious12345 said:
hello all first post and hopefully last post... I have tried to search and search and read and read but still confused on some things. I just have a few questions the confusion comes from instructions how to do things but no reason or explanation why. so anyways here goes I started with no knowledge of any of this so I dont need help with root, and flashing roms or installing and using adb... I have a G1 with pvt board I also plan on using just the linux-swap for now not the compcache one so here goes
1) what is the difference in partitions (ext2 ext3) what is each needed or used for? like your main fat32 is for storing apps and data? one is a ram swap kinda like virtual memory? I just not sure if I would need ext 2 or ext3 or both...I am using hero roms... does the linux-swap partition count as a ext2 or 3? and lastly why do u need to convert a ext2 to and ext3 you cant just create an ext3 off the bat?
2) how do I know if the rom does not say what type of swap it is using as in comp or linux swap? I have read about the user.cfg file but kinda unclear in that... do I have to edit it or just check it from the zip file and see the settings? if so I see downloads for a user.cfg (of course prolly not the settings I need for that rom) but I just edit it and throw it on fat32 partition and it should work automatically? if the rom has compcache working can I still disable it and just use a linux-swap and just change the size of the swap?
3) what is the difference between the user.cfg and userinit.sh?
4) after the rom is flashed (my update.zip) it is ok to delete it off the sdcard?
5) so lastly if I want to put pics / music / videos do I just throw them on the fat32 partition but in what folder so it recognizes it? or do I need to download some kind of file manager to get into the flashed rom so I can see the correct media / download / camera folders and place them there? if I have to go the latter route do I need to do the whole adb "push" thing to get them in there? reason why I ask is with a normal G1 when you connect it with the data cable to your computer i can just see the folders but when rooted and flashed obvioulsy there is nothing to see
6)apps2sd runs and saves on what partition?
please dont kill me I honestly did search and read all over just seems confusing most of the "guides" tell me how to do things but I dont know why those things are usefull or needed to be done
Click to expand...
Click to collapse
1) EXT2 and EXT3 are linux filesystems. If you have an EXT partition on your SD card then this is where apps will be stored. You may notice that if you're running a Hero ROM with no A2SD (/Apps2SD) you will only have about 20mb left for apps. You can make this linux partition as big as you want (within reason). Most people use 512mb, because it's all the space you will ever need for apps.
On to the differences between ext2, ext3 and ext4. Most people use ext3, the reason being is it uses journalling, making it faster and more efficient than ext2. There's nothing wrong with ext2, but ext3 is just a bit better. All ROMs with A2SD support will lit you use ext2 and ext3. Ext4 is less well supported. Personally I use it, just because it's newer than 3, but it's not supported by all ROMs.
So, just got for ext3.
Linux swap is totally different from ext filesystems. As you suggested it is virtual memory, which is essential on Hero ROMs. Personally I use a 64mb partition.
So my 8GB card looks like this
FAT32 - 7.5GB
EXT4 - 500mb
Linux-Swap - 64
2) I think you mean user.conf and userinit.sh. These files tell the ROM what settings to use for Swap and CompCache. It's not essential, just ignore it.
3) user.conf and userinit.sh work together. userinit.sh is one you edit, and user.conf initiates userinit.sh. Again, no ROMs require this, don't worry about it.
4) yeah you can delete update.zip. Personally I keep all my ROMs on the root of the sdcard so I can flash/reflash whenever I want to.
5) You put media on the phones Sd the same way as if it was not rooted. Connect the cable, pull down the notification bar, choose "mount" and drag and drop your files over. Windows won't see your ext partition btw.
6) Apps to sd saves to your ext partition, be it ext2/3/4 ect.
Sorry for the long post just wanted to make sure I answered everything.
3) user.conf and userinit.sh work together. userinit.sh is one you edit, and user.conf initiates userinit.sh. Again, no ROMs require this, don't worry about it.
should be user.conf you edit
If you are willing to learn you can go here http://forum.xda-developers.com/showthread.php?t=542899
AdrianK is right though its not needed ,but it good to know all your options.
AdrianK said:
3) user.conf and userinit.sh work together. userinit.sh is one you edit, and user.conf initiates userinit.sh. Again, no ROMs require this, don't worry about it.
Click to expand...
Click to collapse
actually i think you have this one backwards Adrian. the userinit.sh is what the a2sd script makes a call to upon every boot to activate your linux-swap partition and it uses the various system defaults usually, the userinit.sh then makes a call to the user.conf to see what values it is suppose to use for the various things if they are different then the system default values, and will use the ones in the user.conf. user.conf is the one you edit to change the various values.
or at least this is my understanding of how it works.
ok so basically I just open the zipped rom and see if there is a userinit.sh file in there which means apps2sd is already in the rom... then look at the user.cfg... but do I try to edit the user.cfg before I flash the rom and re-zip it then flash or am I able to edit the user.cfg after I have flashed the rom... I know I believe I am supposed to use the notepad++ to edit it from unbuntu live or is there another way to do it? when I connect and mount my phone in normal working mode not (terminal or console mode) all I see is the update.zip file on there I can not see any of the ext partitions is that normal? as in you can only see your fat32 and what files (music pics) that you put on there? is there any way to view the ext partitions?
like I said if I have an edited user.cfg file with the settings I need do I need to "push" it to the flashed rom via adb? or would it be easier to just edit it then re-zip then flash? oh and by the way what is the direct path to the user.cfg and userinit.sh? as in what folders do they normally reside in?
THANKS you guys are seriously helping me alot soon I will be cooking my own roms.... I just need an understanding of these things not just guides telling me to type stuff even though they work doesnt mean I know whats going on
btw I am trying to use MLIGN-HeroV2.1.6 rom and super laggy for me so I know the partoition sizes are wrong or not working correctly or swap is not enabled....and yes I have an 8g transcend class 6 card... all the others in the thread say its very fast with no major home screen lag and such so I messed up on settings and partions
you must put the userinit.sh and user.conf in /system/sd (your ext3) and chmod 755 both of them.
there are good instructions for using and editing them in the link dan0zone gave you.
the userinit.sh and user.conf (as far as i know) do not come standard in roms, the a2sd scripts reads and runs them on the first boot, more technically the a2sd sends a call out to see if there is a userinit.sh then if there is and if it is the userinit.sh from that link, it then looks at the user.conf to see what values it uses.
i always use pspad to edit my user.conf (and any other android related file) in windows. here is a link to pspad.
Adrian had it right except for the flip flop between user.conf and userinit.sh. You don't want to edit userinit.sh unless you know what you are doing. The user.conf and userinit.sh files are not in the ROM itself. They need to be pushed to /system/sd via adb or terminal emulator. See my signature for the link to the details.
You will not see your ext3 or linux-swap partitions in Windows. You can use adb shell, terminal emulator, a root explorer or Droid Explorer to see those.
Also, if you'd like to edit your user.conf right on your phone, download Text Edit free from the Market.
Here's a big tip. Investigate two scripts. One is called switchrom.sh and the other is called bart.sh which is an update to switchrom.sh. It will save you a lot of headaches later on.
Hope I got it all.
man you guys are great thanks for the replies I think I understand it all now. I will try the pspad and see how that works out although the text edit free seems like a more easier way if your not around a computer... the question I have if I path to /system/sd what if I have an ext 3 and 4 which one would it end up in? ext2 it wont I assume? in some guide I read they say to just put it on the sd card like as in the fat32 part which I know is wrong! or they just didnt explain in further details.... oh god didnt want to get into the chmod 755 cause I didnt think I needed to do that now I will have to go figure out what that does and its purpose... there has been many thread arguments over wether to use chmod 755 I just thought a linux-swap about 96 or so with a swappiness setting of say 60 would be fine didnt think I would need to enable or set up chmod 755
thanks so much!!
dan0zone's link I have read before i can download the userinit.sh file but have no user.cfg to play with are the user.cfg all standard or generic until I or someone else edits them? where can I get a user.cfg file was not in the link dan0zone posted
chmod 755 = -rwxr-xr-x = for a regular file whose user class has full permissions and whose group and others classes have only the read and execute permissions.
there you go. /system/sd is what the directory associated with /dev/block/mmcblk0p2 which is what your ext2/3/4 (doesn't matter) is.
the only thing you need to chmod 755 are the userinit.sh and the user.conf after you place them in your ext2/3/4 partition, and the reason is so that they may run after being called by the a2sd script at boot up.
ok thanks about the chmod 755 I believe i get it seems to be a permissions thing....
any answer on the user.cfg file if it is a generic template file or where to get one unedited?
thanks for the switchrom and bart tip I totally understand that but for now I dont have anything I need to save and backup just doing it bare but in the future i will use those on ce I get better at all of this.... which thanks to all of you i am understanding this ALOT better.....
you can get one from the link that was provided earlier, it shows what the system defaults are beside each of the settings, so if you want to set it all to the system defaults then you can.
ah sorry I am stupid I just saw the title of the userint.sh file I didnt open it too see there was a user.cfg in it.... thanks
I plan to repartition and setup the userinit and user.cfg all over again this is probably the worst question yet but I just plan to stick my sd in my computer and reformat the whole card is that enuff to completly wipe it or will the ext and linux-swap still be in there?
if you are using windows then it will only format the fat32 partition, to get your card back to one partition, you can use parted in the recovery console to rm your partitions then make a single fat32 partition or just rm all partitions then re-make them to whatever size you want.
You can also format your sd card (wipe everything including partitons) by going to Settings, SD Card, Unmount, Format/Erase (not sure what it's called). This seems to work sometimes. You should use parted anyway since you will need to repatition your card there so no need for the extra step. BTW, it's user.CONF not user.CFG. just a heads up if you plan on searching. My signature has all the necessary links to pretty much everything you will need.
AFAIK if the rom has a2sd included, you wont have an option to unmount the sd card.
knowfear said:
AFAIK if the rom has a2sd included, you wont have an option to unmount the sd card.
Click to expand...
Click to collapse
Indeed you are correct, sir. I haven't done it this way since the JF1.51 days. I use either parted command line or GParted on Ubuntu so I didn't even check the settings when I wrote that.
I am having touble disabling swap. I turned off swapper, deleted the .swp file, turned swappiness to 0 in swapper to disable it.
I even tried
su
swapoff /dev/block/mmcblk0p3
Click to expand...
Click to collapse
In terminal, and nothing...
When I go into terminal and check.
su
free
Click to expand...
Click to collapse
It shows I still have swap on.
Can anyone point me into right direction. Or tell me how I can grab userconf file and edit that to disable it.
I really dont want to repartition all over again...
First do
cat /proc/swaps
to make sure that swap in in the the correct place. When i did it I found that it was not in the same place as it was before.
Mines in /dev/block/ramzswap0 not /dev/block/mmcblk0p3
dont have to fully repartition, just grab a ubuntu live cd, and use gparted to blank out the swap partition.... if theres no swap partiton, and no swap file, then there's NO WAY to have swap on... or if you know what your doing boot into recovery and use the CLI gparted there to blank the swap space...
garz said:
I am having touble disabling swap. I turned off swapper, deleted the .swp file, turned swappiness to 0 in swapper to disable it.
I even tried
In terminal, and nothing...
When I go into terminal and check.
It shows I still have swap on.
Can anyone point me into right direction. Or tell me how I can grab userconf file and edit that to disable it.
I really dont want to repartition all over again...
Click to expand...
Click to collapse
Typically, to disable swap, you need to undo what you did to ENABLE it.
And CM does NOT automatically set up swap, so you would have had to intervene manually.
ALTERNATIVELY, you have, not swap, but COMPCACHE -- is you "swap" showing as 24 MB? If it is, you can just go into spare parts to disable it.
I'll ditto that
lbcoder said:
Typically, to disable swap, you need to undo what you did to ENABLE it.
And CM does NOT automatically set up swap, so you would have had to intervene manually.
ALTERNATIVELY, you have, not swap, but COMPCACHE -- is you "swap" showing as 24 MB? If it is, you can just go into spare parts to disable it.
Click to expand...
Click to collapse
Yup, same here with CM7.2, was amazed to find that swap was supposedly still on, but it was compcache I was really worried I'd have a wrecked sd card on my hands
Introducing...
Darktremor Apps2SD 2.7.5.3 Beta 04
Date of Release: January 29, 2011
Download Current Version
Instructions - Change Log - Commands - ROM List - Developer's Guide
Darktremor Apps2SD Fan Page ----
Darktremor Apps2SD Development Group
Are you installing Darktremor Apps2SD on your phone? Here are the instructions to help you: Facebook
Are you a developer wanting to include Darktremor Apps2SD in your latest ROM? Here is the Developer Guide: Facebook
Click to expand...
Click to collapse
Update on Beta 4
It seems I'm getting mixed results with these betas. I'm not sure why this is occurring, some people have been able to get this working right while others have had a hard time with it.
Currently, I'm rebuilding the entire program. This takes a while because I have to figure out how to pack all these options into the program but make it small enough to where it will run correctly.
I will say that some of the beta features are coming back out...one of them is the search for a partition code. I suspect that code may be leading me into issues with certain platforms, so I'm going back to the 2.7.5.2 method of mounting (mmcblk0p2 or mmcblk1p2).
Also, parts of the code will use Busybox Ash (the only code that won't will be starta2sd, which will still use Bash for the time being). The startup code will definitely use Busybox Ash.
Until then, here are the links to the the last two betas and the last official release:
Version 2.7.5.3 Beta 04 - http://www.darktremor.info/files/a2sd/dtapps2sd-2.7.5.3-beta04-signed.zip
Version 2.7.5.3 Beta 03 - http://www.darktremor.info/files/a2sd/dtapps2sd-2.7.5.3-beta03-signed.zip
Version 2.7.5.2-1 - http://www.darktremor.info/files/a2sd/dtapps2sd-2.7.5.2-1-signed.zip
And, if you want past versions, you can view the repository: ftp://dtuser:[email protected] (ignore the smiley face...that's XDA doing that.)
Click to expand...
Click to collapse
Beta 04 took longer than I expected to release. I have done major changes to the code:
1. New commands: convert-ext4 - This will convert your EXT3 partition into EXT4. Just a friendly reminder on this command: Not every rom supports EXT4, so it is possible to go into a boot loop if you switch roms. Use with caution.
2. Reworked convert-ext3 (convert-ext4 gets similar code)...now a flag file is set before the reboot (no conversion is done before the reboot). At load time, the conversion is performed. This takes longer in the reboot process and you may think your phone has locked up...wait about five minutes before doing anything with the phone.
3. Repair is rebuilt...now it uses existing commands to repair the setup (reinstall, remove, cachesd, cachepart, nocache, datasd, nodata). Definitely shrinks the code.
4. Added fix_permissions program to the package. This may help with Superuser issues when using the datasd feature. It is used in reinstall, remove, datasd and nodata.
5. a2sd install is back!!! Both a2sd install and a2sd reinstall do the exact same thing.
6. Dalvik heap code has been shrunk and now creates a file called dalvikheap. Actually, the code has been doing this all along (since about 2.7.5.2, I think), but I never put the code in to use the file.
7. Low Memory Killer code has also been shrunk and uses a file caled dtset_lowmem to set the low memory killer parameter.
8. Replaced Busybox PS function with Toolbox PS. The issue with Busybox PS is that it gives a false reading when I look for android.process.acore (which is the main program when the GUI starts up). If that is present, the program thinks you are trying to run Darktremor without any command line parameters. This was because Busybox would report the process was there when, in reality, it wasn't (validated this when my phone was boot looping.) Toolbox's PS reports the correct setting. This should fix the bootlooping issues some people are experiencing.
9. New commands: usedtbusybox and usedefaultbusybox - these commands may help in diagnosing issues that is may be related to the native Busybox on your rom. a2sd usedtbusybox will use the Busybox that is packaged with Darktremor. a2sd usedefaultbusybox will turn back on the scan behavior of the program introduced in Beta 03.
10. Support for Darktremor Apps2SD version 2.7 and earlier has been discontinued. To upgrade correctly from one of those versions, use version 2.7.5.3 Beta 03b or earlier.
11. Finally fixed stalled boot issues (or at least my tests with several roms says so.)
See the change log for additional details.
You will notice that if the program runs repair and finds a problem, it will correct the issue and reboot. You will see a second reboot when the dalvik-cache clears (this is to fix timing issues with CyanogenMod...I can't control that startup as well as I can other roms). This only happens if repair is ran or you flash a new rom (as repair will realign all data). If you are upgrading from a previous version of Darktremor, you should not see the reboots.
Click to expand...
Click to collapse
This is Darktremor Apps2SD, a multipurpose program that primarily allows a user to execute applications created for the Android OS on their Secure Digital card (with the proper setup...more on that later). But, Darktremor Apps2SD is all about stability. The goal is to be able for all users of the Android OS to be able to take advantage of a method to run their applications from a secure digital card.
But just because the Darktremor Apps2SD is all about stability, doesn't mean it isn't packed with features:
- Move applications (both free and paid) to the Secure Digital card.
- Move Dalvik Cache to run either from your Secure Digital card or from your cache partition and clears the cache on demand.
- Boot Loop Protection: prevents the phone from boot looping in the event the SD card could not be mounted.
- Dalvik JIT for faster performance on Roms which support it.
- User selectable sizes for the Dalvik heap sizes, allowing a user to freely optimize their system.
- Activate a swap partition on your SD card and sets how often the swap partition is utilized.
- Automatically fixes configuration issues.
- Users can check the free space on their SD card and check the installation to make sure all is setup correctly.
- Runs ZipAlign on demand...this makes your programs load faster.
- Built in help system for easy reference of commands.
- All features can also be reversed without repartitioning your Secure Digital card.
- New logging features assists in troubleshooting issues.
- Commands to set the Low Memory Killer feature at boot time. Great for those people who are the "set it and forget it" type.
- And more...
Darktremor Apps2SD is not the same as Froyo Apps2SD. Froyo Apps2SD creates a secure folder on the FAT32 section of your SD card (this is the section that you see when you mount your phone to your computer) and stores the programs there. This is nice as you don't have to do anything special with the phone, but it isn't backwards compatible with older versions of Android (Cupcake, Donut, Eclair) and, because of the way Froyo works, older programs not designed for Froyo will automatically stay on your internal storage (unless you install a program that forces the move to your SD card).
Darktremor Apps2SD takes a different approach. Based on the original CyanogenMod works, Darktremor Apps2SD uses symbolic linking to force Android into moving your applications to the SD card. Because Android will not allow anything to be ran from the FAT32 partition on your SD card (and, in Froyo, it will only allow you to run programs from a special folder), Darktremor utilizes filesystems called EXT2, EXT3 and EXT4. Each one of these filesystems is native to Linux (the operating system running Android), which allows you to run programs from them (same as, say, a computer running Ubuntu). This method is completely compatible with all versions of Android, including Froyo. In fact, you can run both the Darktremor Apps2SD and Froyo Apps2SD at the same time.
Check out the list of Roms that either have Darktremor Apps2SD installed or are compatible with Darktremor Apps2SD. Click on the link labeled ROM List at the top of this message.
Reserved...created because a Tattoo rom has it as part of its build.
I just tried to flash Apps2SD 2.7.5 RC1, but installation fails:
------------------------------------------------
E: Failure at line 48:
set_perm 0 0 0777 SYSTEM:xbin/a2sd
Installation aborted.
-----------------------------------------------
Is there something that I can do?
I love this script. I think I'm going to be using it in the next version of my ROM. Thanks for making it, it's great
It shouldn't do that.
Try the RC3 (about to release it): http://www.darktremor.info/files/a2sd/dtapps2sd-2.7.5-rc3-signed.zip
If that doesn't work, let me know and we go from there. There's a recovery log file that is created...I just have to remember where it is at (was looking at it just this morning).
dancer_69 said:
I just tried to flash Apps2SD 2.7.5 RC1, but installation fails:
------------------------------------------------
E: Failure at line 48:
set_perm 0 0 0777 SYSTEM:xbin/a2sd
Installation aborted.
-----------------------------------------------
Is there something that I can do?
Click to expand...
Click to collapse
alredy running rc3 in our rom hehe
Which rom is that?
danne_jo said:
alredy running rc3 in our rom hehe
Click to expand...
Click to collapse
PuzzleROM
Sent from my Tattoo using XDA App
tkirton said:
Which rom is that?
Click to expand...
Click to collapse
As said before, PuzzleROM
http://forum.xda-developers.com/showthread.php?t=749932&page=10
I saw that during my sweeps of the forums...added into my list.
danne_jo said:
As said before, PuzzleROM
http://forum.xda-developers.com/showthread.php?t=749932&page=10
Click to expand...
Click to collapse
i have installed your APPS2SD on a Tattoo with a shipped non modified rom (I rooted my phone and have ARMON 1.6 recovery though) fine however after the reboot I didn't notice any difference so i checked the with apps2sd check command. here is the output
# a2sd check
a2sd check
[ ] Apps2SD is launching...
[ ] Starting Apps2SD Check Program.
[ ] Searching for Mount Point...
[Ô£ö] Mount point /data/sd located.
[ ] Checking for ext partition
[Ô£û] Ext partition found, but not mounted.
Your rom may not be setup to run Apps2SD.
Check with your rom developer if the boot image
is programmed to run Apps2SD.
Your partition may be using an EXT4 partition,
but your rom may not support EXT4. Repartition
your SD card to use EXT2 or EXT3.
please note i have formatted my sd and have done a ext2->ext3 already.
what should i do now ?
pardol said:
i have installed your APPS2SD on a Tattoo with a shipped non modified rom (I rooted my phone and have ARMON 1.6 recovery though) fine however after the reboot I didn't notice any difference so i checked the with apps2sd check command. here is the output
# a2sd check
a2sd check
[ ] Apps2SD is launching...
[ ] Starting Apps2SD Check Program.
[ ] Searching for Mount Point...
[Ô£ö] Mount point /data/sd located.
[ ] Checking for ext partition
[Ô£û] Ext partition found, but not mounted.
Your rom may not be setup to run Apps2SD.
Check with your rom developer if the boot image
is programmed to run Apps2SD.
Your partition may be using an EXT4 partition,
but your rom may not support EXT4. Repartition
your SD card to use EXT2 or EXT3.
please note i have formatted my sd and have done a ext2->ext3 already.
what should i do now ?
Click to expand...
Click to collapse
Stock ROM doesn't support A2SD as it has no means to execute the script.
Try HCDR.ROM or PuzzleROM
Ahh. Makes more sense now.
Sent from my HTC Tattoo using XDA App
pardol said:
Ahh. Makes more sense now.
Sent from my HTC Tattoo using XDA App
Click to expand...
Click to collapse
Further to your last message i have accidentally found this link where it shows how to move the apps to /system/sd and then all should work.
i have not done anything as such because i am not too familiar with shell scripting and want to avoid to brick the phone.
I know you said APPS2SD does not work with stock roms (not sure why but you are the master here :> ). can this help or there is no way to get it to work ?
actually i noted i am missing a kin d of pre-requisite to complete the script: there is no system/sd entry when using this command so i guess no hope
busybox df -h
busybox df -h
Filesystem Size Used Available Use% Mounted on
tmpfs 93.0M 0 93.0M 0% /dev
tmpfs 4.0M 0 4.0M 0% /sqlite_stmt_journals
/dev/block/mtdblock3 150.0M 139.9M 10.1M 93% /system
/dev/block/mtdblock5 165.1M 142.1M 23.0M 86% /data
/dev/block/mtdblock4 150.0M 3.1M 146.9M 2% /cache
/dev/block//vold/179:1
5.8G 1.8G 4.0G 31% /sdcard
It doesn't work with Stock roms because there's no command in init.rc to launch Apps2SD (which is part of the boot.img). Now, you can modify the boot.img (or get an already modified boot.img) to add support. It will retain the stock rom feel but has a modified boot image.
pardol said:
Further to your last message i have accidentally found this link where it shows how to move the apps to /system/sd and then all should work.
i have not done anything as such because i am not too familiar with shell scripting and want to avoid to brick the phone.
I know you said APPS2SD does not work with stock roms (not sure why but you are the master here :> ). can this help or there is no way to get it to work ?
Click to expand...
Click to collapse
That is because the EXT partition isn't mounted, so Linux (the OS behind Android) doesn't see an EXT partition on the SD card (needs a mount command to be executed, which Apps2SD does, but the rom doesn't launch the program).
pardol said:
actually i noted i am missing a kin d of pre-requisite to complete the script: there is no system/sd entry when using this command so i guess no hope
busybox df -h
busybox df -h
Filesystem Size Used Available Use% Mounted on
tmpfs 93.0M 0 93.0M 0% /dev
tmpfs 4.0M 0 4.0M 0% /sqlite_stmt_journals
/dev/block/mtdblock3 150.0M 139.9M 10.1M 93% /system
/dev/block/mtdblock5 165.1M 142.1M 23.0M 86% /data
/dev/block/mtdblock4 150.0M 3.1M 146.9M 2% /cache
/dev/block//vold/179:1
5.8G 1.8G 4.0G 31% /sdcard
Click to expand...
Click to collapse
i have the same problem and in order to run A2SD i have to mount the EXT3 Partition manually ; anyone knows how to auto mount the ext3 partition at system startup ?!!
ok. i have been able to install a2sd correctly and have it running since a ferw weeks now. The only flipside is i need a PC to be able to reboot the phone since the Ext3 partition does not start.
Is there a command i can put in the init.rc file to autorun a2sd in place of doing a
adb shell a2sd
every time i reboot the phone ?
Hi, how about if after start up , manually mount the ext3 partition and manually run apps2sd app ? As I rarely reboot the system so I think this can be an alternative solution. but could someone let me know the command ? thx