Phone: CDMA Hero
ROM: fresh2.0d
When I installed fresh2.0d rom, I thought it had built in a2sd which I confirmed later by listing apps in /system/sd/app folder. Now my confusion is every time I install an app, I see internal memory size decrease!!!
Is this how it should work? Am I getting my concepts wrong? If it's a problem, is there a fix?
heroid007 said:
Phone: CDMA Hero
ROM: fresh2.0d
When I installed fresh2.0d rom, I thought it had built in a2sd which I confirmed later by listing apps in /system/sd/app folder. Now my confusion is every time I install an app, I see internal memory size decrease!!!
Is this how it should work? Am I getting my concepts wrong? If it's a problem, is there a fix?
Click to expand...
Click to collapse
Some things will write information out to dalvik-cache. By default its on the phone. I went from ~50MB - 130MB after moving dalvik. My new a2sd script will move it http://forum.xda-developers.com/showthread.php?t=667011 but I have only written it for damagecontrol so far.
Also some apps will write to /data/data/ (google earth put 25mb here) this cannot be moved to SD because of upgrade issues.,
TrevE said:
Some things will write information out to dalvik-cache. By default its on the phone. I went from ~50MB - 130MB after moving dalvik. My new a2sd script will move it http://forum.xda-developers.com/showthread.php?t=667011 but I have only written it for damagecontrol so far.
Also some apps will write to /data/data/ (google earth put 25mb here) this cannot be moved to SD because of upgrade issues.,
Click to expand...
Click to collapse
Thanks Treve! Can I remove the file in /data/data/ with command line or will it disrupt anything? Also, are there other places that I can go and delete cache manually?
heroid007 said:
Thanks Treve! Can I remove the file in /data/data/ with command line or will it disrupt anything? Also, are there other places that I can go and delete cache manually?
Click to expand...
Click to collapse
no dont just delete stuff. If your looking to save space cachemate from the market will help. also if you feel like testing damagecontrol + my a2sd with dalvik move changes check out the thread above.
TrevE said:
no dont just delete stuff. If your looking to save space cachemate from the market will help. also if you feel like testing damagecontrol + my a2sd with dalvik move changes check out the thread above.
Click to expand...
Click to collapse
Cool! I will check it out! Thanks again!
Related
MORE INFO IN POST 3 HERE
I am happy to announce the release of my new utility script. This script currently has 11 functions as noted below. It runs in recovery with the help of sdutility which is another script that procures the necessary permissions and file location for some of the features. Some of these options are copied from Cyanogen's various scripts located in his recovery image.
Option 11 will ask you what size to make the swap and ext partitions and then it will partition your sdcard for you using the remaining space for fat32.
The menu looks like this:
Code:
1) Enable SDcard to USB
2) Disable SDcard to USB
3) Upgrade ext2 > ext3
4) Upgrade ext3 > ext4
5) Fix Permissions
6) Repair Filesystem
7) Clear Dalvik-Cache
8) Clear ext partition
9) Backup APPS on ext to FAT32
10) Restore APPS from FAT32 to ext
11) Partition SDcard
Q) Quit Utiltity Menu
Enter Number> _
i am going to get you samuel jackson's wallet from pulp fiction because that is what you are with these scripts.
I think these scripts, along with miketaylor00's fix_rotate script, need to be included in every ROMs /system/bin folders.
Btw, why the . in "./sdcard/sdutility"? I'll probably just move these scripts over to the /system/bin folder on my phone for consistency.
That is an execute command and is required because /sdcard is not in $PATH. sdutility copies the utility script which is the actual script doing all the work to /sbin, setting permissions to 755, and launching it. The point of all of that is with the script on the sdcard it can't partition it without deleting itself.
Fingerlickin said:
That is an execute command and is required because /sdcard is not in $PATH. sdutility copies the utility script which is the actual script doing all the work to /sbin, setting permissions to 755, and launching it. The point of all of that is with the script on the sdcard it can't partition it without deleting itself.
Click to expand...
Click to collapse
I follow... guess I can just keep it on SDcard to run it from.
I looked at the files and figured that's how it worked... I did copy utility to my system/bin and ran it from recovery console. I even backed up my apps using option 9. It gave me an access denied error from line 173 (the fi command in the script). However, it seems it did back up the apps.
dude, this is awesome. im gunna try it out later... using my ubuntu partition.
anyways, when you backup your apps from the ext partition, does it copy over the google apps as well?
backing up the apps copies the /system/sd/app folder to /sdcard/appbackup.
To the best of my knowledge this is NOT a violation because you are backing up your OWN apps including any closed source apps. As long as you don't distribute these apps you are fine.
P.S. I bought a movie tonight and immediately put it in my computer and ripped it. My reason for this is my computer stores all my movies and my xbox streams them to my TV. Nothing wrong with this because I am not distributing the movie to other people.
Fingerlickin said:
backing up the apps copies the /system/sd/app folder to /sdcard/appbackup.
To the best of my knowledge this is NOT a violation because you are backing up your OWN apps including any closed source apps. As long as you don't distribute these apps you are fine.
P.S. I bought a movie tonight and immediately put it in my computer and ripped it. My reason for this is my computer stores all my movies and my xbox streams them to my TV. Nothing wrong with this because I am not distributing the movie to other people.
Click to expand...
Click to collapse
hey finger, let your xbox stream video to my tv as well.
Fingerlickin said:
backing up the apps copies the /system/sd/app folder to /sdcard/appbackup.
Click to expand...
Click to collapse
I feel the urge to clarify this.
mounts both ext and fat32
check to see if both folders exist and creates /sdcard/appbackup if it doesn't
THEN it copies the CONTENTS OF /system/sd/app to /sdcard/appbackup
but david, I'm a good law abiding citizen and that would be illegal.
catch me on gtalk
So has anyone else had the access denied error referencing line 173?
Fingerlickin... any chance you could work with Cyanogen to integrate this with his recovery? I'm thinking it's time for a Cyanogen Recovery v1.5.
Great work fingerlickin
Unasari, the orig plan for this was to make cyan's recovery more noob friendly, hopefully cyan will roll this into his new recovery and add trackball support to it for the mt3g users. Don't be surpised if you see a wrecking crew modified recovey image
Great work I see all of us got something to keep us busy now.
I am looking into the line 173 error now. We need MT3G support before cyan will touch it, working on that too.
I can't recreate the error at line 173. Lets see if others have the problem as well.
Updated to v1.1 see post 3 HERE for details.
This has a possible fix for your line 173 error. I didn't anticipate someone trying to backup apps when they don't have any apps installed on the ext or you try to backup apps after partitioning the card because there obviously isn't a /system/sd/app directory in this case. I have no idea if this will fix your problem or not.
I also included support for ADB (MT3G) YAY
Updated again.
v1.2
updated to fix_permissions v1.29
fix_permissions always has the -r option
Hello XDA team
First of all, I think that this is the appropiate forum for this question, but if it doesn´t, please feel free to move to the correct thread.
I have a spanish Vodafone HTC Magic (32B) and after several combinations I have found that the most suitable partition system for my SD card is Fat32 + 128 MG of Swap. I really hate a2sd and Ext partitions because my device doesn´t really need them, and it only mess my apps.
I´m searching a way to disable a2sd from the .zip files of ROMs in order to be able to install in my phone, but I´m not sure hot to made it
If I take, for example, MightyMax latest ROM (MghtyMax1.9.1) and extract the contents, I find "a2sd" under /system/bin, so, if I remove this app and zip again the ROM, will I be able to "Skip" this feature? should I edite the user.conf and or userinit.sh files?
Many thanks for your help
Rgds
If its a question it goes to Q&A no matter what type of question it is. Just an FYI ^_^
u can try it. I dont know if it will work or not. Just remove all traces of a2sd and resign the update.zip. The other thing is, u can just not have an ext2 partition. That will disable a2sd from the first boot...
nephron said:
u can try it. I dont know if it will work or not. Just remove all traces of a2sd and resign the update.zip. The other thing is, u can just not have an ext2 partition. That will disable a2sd from the first boot...
Click to expand...
Click to collapse
The problem is that ROMs that require a2sd won´t boot (tried MLGIN, MightyMax, Sense Hero..) with my partition layout, they all keeps in the boot screen
thats because u they want ur layout to be like this
fat32,ext2,swap
the only thing u can do is
fat32,ext2,swap
then remove ext2 leaving a gap. After that, expand your fat32 to cover over the ext2.
so ur new layout would be fat32,swap but the swap partition would be on the third partition... (i think )
You could try using the script included in Wes Garner's update here to disable A2SD (should be able to replace the script in the update file of the ROM you are using).
Moved to Q&A
daveid said:
You could try using the script included in Wes Garner's update here to disable A2SD (should be able to replace the script in the update file of the ROM you are using).
Click to expand...
Click to collapse
Many thanks Daveid, sound very interesting, I will give it a try later..
I tried re-build the MghtyMax ROM removing the a2sd bin file and adjusting the user.conf and userinit.sh files but after installing the "new" ROM (it installs just fine) the phone keeps forever in the "Vodafone" bootscreen... Any ideas??
Rgds
iamarock said:
Many thanks Daveid, sound very interesting, I will give it a try later..
I tried re-build the MghtyMax ROM removing the a2sd bin file and adjusting the user.conf and userinit.sh files but after installing the "new" ROM (it installs just fine) the phone keeps forever in the "Vodafone" bootscreen... Any ideas??
Rgds
Click to expand...
Click to collapse
Your SD card has three partitions right? And, why remove the a2sd bin file? I would use the modified script I linked you to, make a very small ext2 partition - so you can put your user.conf & userinit.sh files on it, and see what that does.
What is the logcat (or ddms) output during boot up?
daveid said:
What is the logcat (or ddms) output during boot up?
Click to expand...
Click to collapse
Sorry but I think that I'm a newbee with this kind of issues, how can I get the boot logs???
Many thanks
daveid said:
Your SD card has three partitions right? And, why remove the a2sd bin file? I would use the modified script I linked you to, make a very small ext2 partition - so you can put your user.conf & userinit.sh files on it, and see what that does.
What is the logcat (or ddms) output during boot up?
Click to expand...
Click to collapse
Sorry guys but nothing seems to work for me...
-I have tried to disable a2sd editing the user.conf file and re-building the ROM. Nothing happens. The "new" ROMS installs just OK but it keeps forever in the Bootscreen logo
-The script mentioned by daveid in entry #5 neither seems to work for me, same bootloop
Any ideas??
Many thanks in advance, this is a very annoying issue for me
Anyone can help me with this issue?
Many thanks in advance
Rgds
iamarock said:
Sorry guys but nothing seems to work for me...
-I have tried to disable a2sd editing the user.conf file and re-building the ROM. Nothing happens. The "new" ROMS installs just OK but it keeps forever in the Bootscreen logo
-The script mentioned by daveid in entry #5 neither seems to work for me, same bootloop
Any ideas??
Many thanks in advance, this is a very annoying issue for me
Click to expand...
Click to collapse
Please, please, anyone can help me with this request? I tried to install the amazing Kink's Droid Eris port without sucesss, i guess that again due the a2sd issue
Is there any way to remove a2sd or to skip ext2 requirements when installing a rom?
Many thanks in advance
Best regards
Recently, I started getting a "not enough storage available" error when trying to install Handcent either from the Market or using a Titanium restore. I know it's not a space issue because all other apps that I have tried install with no problem. I am using A2SD and have about 400 MB free. I have duplicated this error on multiple ROM's so it must be something on my phone. I searched and found something about permissions on *.so files in the lib directory but I don't know enough to fix it myself. Here is a pastebin of the error:
http://pastebin.com/33gKG5Db
Any help is greatly appreciated!
PS - link to the post that talked about the lib perm's - http://forum.xda-developers.com/showpost.php?p=6240715&postcount=5
PROBLEM SOLVED!
wjason said:
Recently, I started getting a "not enough storage available" error when trying to install Handcent either from the Market or using a Titanium restore. I know it's not a space issue because all other apps that I have tried install with no problem. I am using A2SD and have about 400 MB free. I have duplicated this error on multiple ROM's so it must be something on my phone. I searched and found something about permissions on *.so files in the lib directory but I don't know enough to fix it myself. Here is a pastebin of the error:
http://pastebin.com/33gKG5Db
Any help is greatly appreciated!
PS - link to the post that talked about the lib perm's - http://forum.xda-developers.com/showpost.php?p=6240715&postcount=5
Click to expand...
Click to collapse
I know this is a stupid question but ur not trying to install when card is mounted to computer r u. Also what app2sd r u using, is ur ext partition full, I've also noticed this when I thought I had room then went in and deleated a few old nandroids and then it worked great.
I had the same problem.
Go to Applications
Somewhere in there, there is a handcent registry that is different than the normal handcent program.
Scan through everything, you will find something like com.sms.handcent. Uninstall that as well as the program and you should be able to install.
Bielinsk said:
I had the same problem.
Go to Applications
Somewhere in there, there is a handcent registry that is different than the normal handcent program.
Scan through everything, you will find something like com.sms.handcent. Uninstall that as well as the program and you should be able to install.
Click to expand...
Click to collapse
I see it under applications but every time I click on it I get a f/c on settings (I get the f/c if I click on anything under applications that begins with com.). Any way to do it through ADB? I checked system/sd/app and didn't see the com.handcent.nextsms to remove?
wjason said:
I see it under applications but every time I click on it I get a f/c on settings (I get the f/c if I click on anything under applications that begins with com.). Any way to do it through ADB? I checked system/sd/app and didn't see the com.handcent.nextsms to remove?
Click to expand...
Click to collapse
you have gtalk?
if so add me [email protected]
I'll try my best to help out
regaw_leinad said:
you have gtalk?
if so add me [email protected]
I'll try my best to help out
Click to expand...
Click to collapse
Problem solved - Thanks Regaw!!!!
Well hell, what was it?
Make the search usefull
There was an old data entry in /data/data called com.handscent.newsms or something, and I deleted it. then it worked perfectly.
regaw_leinad said:
There was an old data entry in /data/data called com.handscent.newsms or something, and I deleted it. then it worked perfectly.
Click to expand...
Click to collapse
yep... I have had this problem with a couple of apps. The real fun is sometimes that directory is named something completely different then the application name. Then you have to guess at what it is and then check /data/apps to verify it has a missing apk.
Froyo sux....with apps i get all types of complications...ive done everything re-format and used all methods...no A2SD method works including Google's. I want the Old Method on the Ext.....but not even Rodriguez' works...anyone solutions or people suffering? cuz its either i cant put all my apps or they dont install....i even had a 'Contact Storage' problem where it bloated so big...my phone said i had low memory
+1
Anyone has a working solution for FRF50?
how bout you wait till froyo source is out then when can have all kinds of goodies
teflon252 said:
Froyo sux....with apps i get all types of complications...ive done everything re-format and used all methods...no A2SD method works including Google's. I want the Old Method on the Ext.....but not even Rodriguez' works...anyone solutions or people suffering? cuz its either i cant put all my apps or they dont install....i even had a 'Contact Storage' problem where it bloated so big...my phone said i had low memory
Click to expand...
Click to collapse
Try this rom
http://forum.xda-developers.com/showthread.php?t=644438
I'm not sure but I heard that Froyo doesn't like EXT partitions ...
Perhaps the kernel on the upper link should work. Give a try =)
i'm trying it now....let u kno how it works..and thanks for the suggestions
NO LUCK....DOESNT EVEN READ EXT PARTITION...I DUNNO what the hell KING is talking about
I have stock rooted froyo, and the apps that can be pushed to the sd card go to the fat32 part.
I have not tried using a2sd yet.
I will try pushing an app thru adb tonight to sd and see if it installs.
Update: I installed a couple of apps to the sdcard with ADB. One I don't use anymore, and one that I had installed from the market. I had to uninstall Google Earth, but I now have it installed on the sdcard and it is working just as well as if it were on the phone. Also tried Tower Raiders Free, and it also installed to the sdcard and plays with no problems. So I don't know if froyo needs the ext partition or not, but the newest ADB release does not in order for apps to work.
the benefit of EXT is space and i already have so many apps installed already from previous....the new method allows me only half and i would have to re-install all and for some reason...regular froyo doesnt sit well with my phone....like in 'manage application' it just says calculating...and i can never install certain apps
paul's (MoDaCo) r16 + have apps2sd on ext partition as an option.. i've been using it on ext4 since r16 dropped have about 75 apps including google earth and flash and have 135mb left on internal .. advanced task manager says 223mb with 20 apps running
did u have to activate the option? and how?
no .. its automatic... there are 2 ways... google (froyo) crappy apps2sd and our way of doing things.. just have your sd card fat32 /ext2/3/4 and thats it .. disregard the google froyo a2sd
You can try Darktremor A2SD and see if that works.
The rom you are on would need to have some form of a2sd launch command in the init.rc. In the old stuff, it would be a matter of putting the following lines in the init.rc:
1. Look for a line called class_start default. Add the next two lines above the class_start line:
start a2sd
on property:cm.filesystem.ready=1
2. Go to the end of the file and type the following:
service a2sd /system/bin/logwrapper /system/bin/sh /system/bin/a2sd
disabled
oneshot
Now, I'm not sure about Froyo and its Apps2SD...I'm not sure if you need to find the lines in init.rc (assuming they are actually in that file) and comment them out.
But try the program and see if it works.
http://www.darktremor.info/files/a2sd/a2sd-2.7-2-signed.zip
teflon252 said:
Froyo sux....with apps i get all types of complications...ive done everything re-format and used all methods...no A2SD method works including Google's. I want the Old Method on the Ext.....but not even Rodriguez' works...anyone solutions or people suffering? cuz its either i cant put all my apps or they dont install....i even had a 'Contact Storage' problem where it bloated so big...my phone said i had low memory
Click to expand...
Click to collapse
+1 (topic)
Anyone tried the above post on froyo?
A link to step by step instructions will be appreciated.
Some steps here: http://wiki.cyanogenmod.com/index.php/Apps2SD but dont know what else is needed for froyo.
I want this because my /data partition is completely out of space, and no more apps can be moved using the froyo method.
Forcing all apps to install by default on the sd card is buggy at best.
update: works, see the below post, http://forum.xda-developers.com/showpost.php?p=6952103&postcount=16
Is SWAP partition still necessary ?
I've read that swap is not needed. Works without one for me
@britoso - i see you talk of this file - a2sd-2.7-update3-signed.zip - is that a rom?
milomak said:
@britoso - i see you talk of this file - a2sd-2.7-update3-signed.zip - is that a rom?
Click to expand...
Click to collapse
its a flashable update that installs the a2sd components to your system.
Here is the thread, first message has instructions: http://forum.xda-developers.com/showthread.php?t=670087
britoso said:
+1 (topic)
Anyone tried the above post on froyo?
A link to step by step instructions will be appreciated.
Click to expand...
Click to collapse
just wanted to note that this works fine on Froyo FRF83 too.
I used Paul Obrien's FRF83 rooted, deodexed rom.
1)nandroid+ext
2)flash frf83
3)flash apps2sd
4)reboot
5)bootloop!
to fix it:
Code:
adb remount
adb shell mkdir /system/sd
adb shell
/system/bin/a2sd install
a2sd repair
a2sd check
6)success!
edit: it does not start automatically on reboot, flash leofroyo's boot.img in bootloader mode to fix it
fastboot flash boot leofroyoboot.img
Click to expand...
Click to collapse
Tried firefox for android beta2 today and it freezed my phone, so I uninstall it only to realise that it locked 13MB of my internal memory permanently probably due to bad uninstall. Tried to reinstall it so that I can uninstall it again but it didn't allow me to install again saying that I don't have enough memory (though i still have ~45 MB free internal memory).
Anyone knows where does firefox install to? I couldn't find it in any of the app directory (not in data\app or system\app, nothing in dalvik cache and data\data as well). having 14MB memory locked is really a paint considering how small our milestone memory is.
Please help.
Thanks
en0203 said:
Tried firefox for android beta2 today and it freezed my phone, so I uninstall it only to realise that it locked 13MB of my internal memory permanently probably due to bad uninstall. Tried to reinstall it so that I can uninstall it again but it didn't allow me to install again saying that I don't have enough memory (though i still have ~45 MB free internal memory).
Anyone knows where does firefox install to? I couldn't find it in any of the app directory (not in data\app or system\app, nothing in dalvik cache and data\data as well). having 14MB memory locked is really a paint considering how small our milestone memory is.
Please help.
Thanks
Click to expand...
Click to collapse
bump. please can someone help. thanks
en0203 said:
bump. please can someone help. thanks
Click to expand...
Click to collapse
1.Do you have a recent nandroid backup? that would be a simple fix?
2. What rom and kernel are you using?
3. Is your phone rooted? Probably yes...All the apps go to /system/app, unless you have apps2sd installed
4. If it's not there and it's not in "manage applications" then probably it's a an error of your rom showing erroneous available space.
Hi,
Thanks for your reply.
1) I am using XT720, we don't have nandroid backup tools yet
2) Stock EU rom and kernel for XT720
3) yes, rooted. I am sure it's not in /system/app (mine has got apps2sd)
4) I guess I'll probably need to reflash the rom to get rid of it then. a bit troublesome but no choice I guess.
Something about the firefox is that if you install it you'll find that the space taken up by the firefox is much bigger than the .apk+dalvik cache+data in the normal app installation path. some portion gets installed into somewhere else which nobody knows where. My friend with a Nexus one try to move it to sd but it simply won't move the whole thing because part of it does not install to the /app.
Anyway, thanks for the help. I'll wait another day or two before I flash it to stock again.
Many thanks
en0203 said:
Hi,
Thanks for your reply.
1) I am using XT720, we don't have nandroid backup tools yet
2) Stock EU rom and kernel for XT720
3) yes, rooted. I am sure it's not in /system/app (mine has got apps2sd)
4) I guess I'll probably need to reflash the rom to get rid of it then. a bit troublesome but no choice I guess.
Something about the firefox is that if you install it you'll find that the space taken up by the firefox is much bigger than the .apk+dalvik cache+data in the normal app installation path. some portion gets installed into somewhere else which nobody knows where. My friend with a Nexus one try to move it to sd but it simply won't move the whole thing because part of it does not install to the /app.
Anyway, thanks for the help. I'll wait another day or two before I flash it to stock again.
Many thanks
Click to expand...
Click to collapse
Can you go into recovery? ADB commands actually work as root there.
You also said you have app2sd - I'm guessing the ext version. You can browse around the ext partition if you have something that can read it (like Ubuntu) and delete it from the card as well.
- Look into your /cache partition and delete every download*.apk
- Look into /data/app and look if there is still an apk left
- Look into /data/data and see if a Firefox-folder is located there - delete it!
You can do all this with RootExplorer
Then you should be fixed
Milestone isn't supported. I think I read it somewhere on the mozilla site. There's some known issue logged somewhere
Sent from my Milestone using XDA App
Check if there is any "*.tmp" files under /data/app ?
I was locked some memory due to unsuccessful install of "Pocket Legends", and found out that the apks were stored in both "/cache/downloadfile.apk" and "/data/app/vmxyzxyz.tmp".