Related
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.
what's the difference between the two installers?
The advanced installer uses updater-script, the same method that Cyanogen uses for CyanogenMod.
The other script is the standard update-script, for compatibility with older recovery programs.
Other than that one difference, they are identical.
hi2u2 said:
what's the difference between the two installers?
Click to expand...
Click to collapse
Bump...new version released: 2.7.5.2
why is it i have to run a2sd repair just to get this to boot otherwise it chokes out
http://pastie.org/1197625
rom: ported 2.2 sensui rom on droid1
using 512ext3 partition as mmcblk0p2 with the init.d startup method(same issue with the init.rc methed, not like that would matter)
Do you have a /data/dta2sd.log file? That would help me more than the log file you sent (the adb logcat is too late in the process for me to see what Darktremor is doing).
If you have the log file, send it to me at [email protected] and I'll see if I can find out what's going on.
EDIT: Jr33 may also be able to help out on this...he's got this working in two Motorola roms, so he may have to do something special with the rom to get the program to start. It may be a similar situation that I'm running into for the Samsung Galaxy S platforms.
jamezelle said:
why is it i have to run a2sd repair just to get this to boot otherwise it chokes out
http://pastie.org/1197625
rom: ported 2.2 sensui rom on droid1
using 512ext3 partition as mmcblk0p2 with the init.d startup method(same issue with the init.rc methed, not like that would matter)
Click to expand...
Click to collapse
Just want to make sure...
I am running Liberated R010. I have partitioned the class 4 sd card, in this order...6.5GB FAT 32, about 1GB Ext2, about 32MB Linux Swap. I have copied all of my old sd card into the 6.5GB partition. I'm wanting to stick this into the phone and let it do its thing. Will the apps be moved automatically? What control will I have during and after this big moment?
Do I need to reboot with the new card or can I do the unmounted hotswap?
Sent from my (liberated) HTC Liberty using XDA App
Apps will be moved automatically if the ROM supports A2SD+ or Apps2SD (Liberated should).
Not sure what you are meaning regarding "control". The move is pretty quick and happens at the start of the boot process. Technically, the user doesn't have control of the phone at this point.
duckredbeard said:
I am running Liberated R010. I have partitioned the class 4 sd card, in this order...6.5GB FAT 32, about 1GB Ext2, about 32MB Linux Swap. I have copied all of my old sd card into the 6.5GB partition. I'm wanting to stick this into the phone and let it do its thing. Will the apps be moved automatically? What control will I have during and after this big moment?
Click to expand...
Click to collapse
No...no hotswapping. The EXT2 or EXT3 partition is mounted...you could corrupt it. You will need to reboot with the card as the mounting of the EXT2 / EXT3 partition happens during boot time.
duckredbeard said:
Do I need to reboot with the new card or can I do the unmounted hotswap?
Sent from my (liberated) HTC Liberty using XDA App
Click to expand...
Click to collapse
I did tried as you recommended and nothing changed except for the size of the SD card. The partitioned card showed as 6.6GB, (instead of the full 8ishGB) but the internal memory stayed at 185MB. I used the live ubuntu method, 6.6GB fat 32, 1GB ext2, 32MB Linux. Partition session showed as successful.
Sent from my (liberated) HTC Liberty using XDA App
Okay, try this:
From the adb shell, type a2sd reinstall.
The reason for this is that, if you were running Darktremor without the SD card partitioned, boot protection would activate and set the NoA2SD flag.
a2sd reinstall will clear the flag and move the apps to the SD card. That should fix your issue.
duckredbeard said:
I did tried as you recommended and nothing changed except for the size of the SD card. The partitioned card showed as 6.6GB, (instead of the full 8ishGB) but the internal memory stayed at 185MB. I used the live ubuntu method, 6.6GB fat 32, 1GB ext2, 32MB Linux. Partition session showed as successful.
Sent from my (liberated) HTC Liberty using XDA App
Click to expand...
Click to collapse
Now that I'm on a real keyboard, I can better explain what got me to this point. Some of this you've heard before.
I did Nandroid backup, then copied all of my SD to a safe place on my PC. Partitioned the new Class 4 SD card using Linux LiveCd, with about 6.5GB Fat32, 1GB Ext2, and 32MB Linux swap. It took a few tries, I'm not a Linux person. Once It was successful, I went back into windows and looked at the card size. It was indeed about 6.5GB.
Powered off the Aria and inserted the SD card, then powered on like normal. No obvious change, other than the SD being smaller. No change to the internal storage. Found the darktremor .zip file and copied it to the root of my SD using a card reader, reinserted the SD (with power off) and rebooted in recovery, applied your .zip. Phone rebooted fine, again no changes.
I again tried to partition the card using ROM Manager, which had previously been unsuccessful on the new card. After it had been Linux partitioned the one time, ROM Manager seemed to have worked. I'd rather have more than 512MB Ext2, though.
I am perilously close to full on my internal storage, so I'm eager to get this going. Thanks for your replies.
hey tkirton,
upon installing 2.7.5.2 and running 'a2sd check', I see that swap does not start now ('partition not present or no swap support').
I installed it by rebooting into recovery and flashing the zip, same way I have been doing up until now.
Any ideas?
So, you setup the SD card via Rom Manager and all is working, but it didn't work via Linux LiveCD, correct?
It could be the EXT2 partition. It works, but because there is no journaling, the partition is more susceptible to corruption.
You may try the LiveCD method again. This time, create a 1GB EXT3 partition and make sure you unmount the partition before removing it (force removal while it is mounted is a good way to corrupt an EXT2 partition...can also corrupt an EXT3 partition). Don't worry about going into Windows to validate...you can do that with your phone.
I don't know if there is another recovery available to you. I run GodSpeed (based on Amon_RA's recovery) on my Hero and Amon_RA on my Evo. I know the Amon_RA recovery will allow you to select your EXT2/EXT3 size.
duckredbeard said:
Now that I'm on a real keyboard, I can better explain what got me to this point. Some of this you've heard before.
I did Nandroid backup, then copied all of my SD to a safe place on my PC. Partitioned the new Class 4 SD card using Linux LiveCd, with about 6.5GB Fat32, 1GB Ext2, and 32MB Linux swap. It took a few tries, I'm not a Linux person. Once It was successful, I went back into windows and looked at the card size. It was indeed about 6.5GB.
Powered off the Aria and inserted the SD card, then powered on like normal. No obvious change, other than the SD being smaller. No change to the internal storage. Found the darktremor .zip file and copied it to the root of my SD using a card reader, reinserted the SD (with power off) and rebooted in recovery, applied your .zip. Phone rebooted fine, again no changes.
I again tried to partition the card using ROM Manager, which had previously been unsuccessful on the new card. After it had been Linux partitioned the one time, ROM Manager seemed to have worked. I'd rather have more than 512MB Ext2, though.
I am perilously close to full on my internal storage, so I'm eager to get this going. Thanks for your replies.
Click to expand...
Click to collapse
Hmmm...works for both my Hero and Evo.
Which rom are you using? If you are using /dev/block/mmcblk1p3, it should work as it was introduced in this version.
I know this is going to sound stupid on my part, but are you sure swap has been working? The reason I ask is that earlier versions of CyanogenMod 6 Nightly Builds had the swap turned off in the kernel...of course, I didn't know that until I was working on another version of Darktremor (and I had already used three different versions of CyanogenMod prior to that).
hi2u2 said:
hey tkirton,
upon installing 2.7.5.2 and running 'a2sd check', I see that swap does not start now ('partition not present or no swap support').
I installed it by rebooting into recovery and flashing the zip, same way I have been doing up until now.
Any ideas?
Click to expand...
Click to collapse
I never got any different result from any method I tried. Except that after one attempt my Tasker widgets had lost their icons. I've put a lot into Tasker lately, which may explain my internal storage getting full.
I shall reattempt the Linux and pay particular attention to the mount status. I will also go with Ext3 if it is not a conflict with darktremor. Will the phone's storage be shown in addition to my partition (185+1024)? If my ROM (Liberated Aria R010) has DT A2SD, should I still install from .zip?
Sent from my (liberated) HTC Liberty using XDA App
Try flashing this one first: http://www.darktremor.info/files/a2sd/dtapps2sd-2.7.5.1-adv-signed.zip
That is 2.7.5.1...the first release was bugged...this is release 2. I don't know which one does Liberated Rom have.
If that works, then jump up to 2.7.5.2. Make a backup so you can restore if something goes wrong.
duckredbeard said:
I never got any different result from any method I tried. Except that after one attempt my Tasker widgets had lost their icons. I've put a lot into Tasker lately, which may explain my internal storage getting full.
I shall reattempt the Linux and pay particular attention to the mount status. I will also go with Ext3 if it is not a conflict with darktremor. Will the phone's storage be shown in addition to my partition (185+1024)? If my ROM (Liberated Aria R010) has DT A2SD, should I still install from .zip?
Sent from my (liberated) HTC Liberty using XDA App
Click to expand...
Click to collapse
tkirton said:
Hmmm...works for both my Hero and Evo.
Which rom are you using? If you are using /dev/block/mmcblk1p3, it should work as it was introduced in this version.
I know this is going to sound stupid on my part, but are you sure swap has been working? The reason I ask is that earlier versions of CyanogenMod 6 Nightly Builds had the swap turned off in the kernel...of course, I didn't know that until I was working on another version of Darktremor (and I had already used three different versions of CyanogenMod prior to that).
Click to expand...
Click to collapse
I am using /dev/block/mmcblk0p2. Followed the instructions here: http://forum.xda-developers.com/showpost.php?p=7372509&postcount=9
Ok...tried it again. Here's exactly what I did: Linux liveD method partition: 6.7GB Fat32, 1GB Ext3, 32MB Linux swap. I was sure I did the mount thing as well. Did nandroid backup then copied my old card (entirely) into the new Fat32. Stuck the new card into the powered off phone and booted into recovery. Installed the zip you posted in this thread. After install (with no problems) I reboot phone and no change to the indicated internal storage capacity. I am running liberated aria r010 which is purported to include dta2sd, but disabled by default. If this is my issue, how do I enable it?
Sent from my (liberated) HTC Liberty using XDA App
Hi,
I have a problem with data space.
Therefore I removed those aplications from system folder :
Swype.apk (11 MB) - for czech and many other user useless because of absence their language support
Layar.apk (5MB) ? - useless too - I do not wanna anyone know where I am located
Samsung Apps.apk (5 MB ?) - useless because Samsung GAY policy
Thinkdroid.apk ( 5 MB) ? - I never used , but I wanna install it on sdcard - weird after remove from system, it was not possible to install it - phone rebooted
Ive expected I will have more free space for aplications, but I have not
So I have now :
System : 182.99 MB used, 27.64 MB free
Data : 188.86 MB used , 5.29 MB free
Cache : 792 KB used 32.03 MB free
My goal is ofcourse to have as much as MB free at DATA folder / partition
Is there any EASY way how to make it happen without data loss and most important - without PHONE BRICK ?
so some partition manager ?
I tried already some trick to have 2 partitions on SD and ofcourse, it does not work - it take only 1 or more hours to get 30+ GBs of music, maps etc back to SD
I am not sure if this works for example at Kyrillos 7.0 , but if I have to download something over DATA connection and cant use wi-fi , then this solution is unacceptable
Of course my goal is to have unchanged aplications and their data + I5800XXJPS
My dream is Android 2.3.4 , but I will wait till FM RADIO and other non working stuff will be solved
I found this http://android.modaco.com/topic/331205-guide-how-to-get-more-free-space-for-your-apps/
but it looks too hard and I need more like 128/136 MB for system partition
I am using APP 2 SD Pro and Move2SD Enabler set to EXTERNAL
for example install ANGRY BIRDS is impossible even I have 200 MB free at my 32 GB SDCARD
thanks for your help
Bro, wrong section.
And you have a 32 GB SD card. Then make a 1 GB ext4 partition. Rest 31 GBs you use for songs and all. Kyrillos has apps2sd v2 enabled. Only /data/data/ remains in internal memory. If you don t want that to also, then you can use app2sd v3. It works. All apps that you install will goto ext4 partition of SD.
It may be possible but there is an easier way. If you are low on space for apps, that means that data partition is full, you on the other hand, you deleted apps from system partition so you have more space there. So... go to data/app and move some of your instaled apps from there to system/app. Be sure to leave some free space on system partition, especially if you are going to change themes, then leave 10mb free.
thanks
ka'cipeder said:
It may be possible but there is an easier way. If you are low on space for apps, that means that data partition is full, you on the other hand, you deleted apps from system partition so you have more space there. So... go to data/app and move some of your instaled apps from there to system/app. Be sure to leave some free space on system partition, especially if you are going to change themes, then leave 10mb free.
Click to expand...
Click to collapse
Thanks all to respon, specially You,
I alraedy did exactly You suggest and it helps
I do not wanna go ext partitions, I alraedy deleted some most biggest size files from Dalvik-cache too
if there are a some steps how make works APP2SD ver 3 without partitioning SD, then please write how
now I am trying Regina Launcher first time, initializing takes so loooong
Best Regards
Radek
Hi all,
So last night I decided to give Cyanogenmod7 a try. I came from MIUI.us 2.1.20 - I just love MIUI, but it's a bit too demanding for the Milestone. So I have CM7 up and running, and it is a lot more snappy. But now, I'm having trouble installing some apps.
I tried installing my bank's banking app, but it didn't install - checked the market and it doesn't appear. Same thing with WhatsApp!! If it were working, I might just become a CM7 user..but it's not working.
Am I missing something? I installed after doing a full wipe, after which I installed DT A2SD scripts and then gapps-20111216 (although didn't see gmail or market etc after gapps, so installed those via apk).
What's the deal here?
Thanks.
Sent from my Milestone using Tapatalk
Ok, just wiped again, and reinstalled all. CM7 then gapps then dt a2sd. So far it's working.
Sent from my Milestone using Tapatalk
googleservicesframework.apk and vending.apk are all you need for using market. Try to reinstall them. May you success.
Ok, so now my problem is A2SD. It's not working! A2SDGUI refuses to go in, and when I do a check, I get a segmentation fault...I've never had this issue before. I've tried reinstalling DT A2SD from withing recovery and still, nothing. Please assist, I just need to get set up properly now.
Regards
Sent from my Milestone using Tapatalk
DT scripts dont work ...use an external partition (app2ext)
d.casper.b: CM7 for Milestone already comes with its own ap2ext scripts that are automatically used if there is ext partition present on your sdcard.
You should not install any 3rd party app2ext scripts as they are very likely to be conflicting with the scripts that are already there.
Thanks kabaldan.
I'll check it out.
I was even going so far as trying to use Link2SD from the market..
How'd I know if it's working? By monitoring the available internal storage?
Sent from my Milestone using Tapatalk
d.casper.b said:
Thanks kabaldan.
I'll check it out.
I was even going so far as trying to use Link2SD from the market..
How'd I know if it's working? By monitoring the available internal storage?
Sent from my Milestone using Tapatalk
Click to expand...
Click to collapse
when you will enable app2ext you will see the total space in your storage rise to 197 mb
I am not winning. I did a factory reset and flashed cm7 and gapps (not dt a2sd).
I did a test, internal storage was at 191mb, then I installed opera mobile and it went down to 182mb. Then uninstalled it again. Went into cyanogenmod settings and set install location to external. Installed opera again, but it was no different. Moving it to sd under 'manage applications' increased the internal memory again, but that's just moving the app to the FAT32 partition of the sd card.
So it's not seeming to work for me for some reason.
Sent from my Milestone using Tapatalk
EDIT: I really don't want to be a nuisance, but now, looking at the available storage using "Quick System Info", I noticed after uninstalling "Opera Mobile", 9mb was freed on internal storage & 13mb on the ext partition.
So, perhaps it is working, and since the dalvik cache is (I assume) on internal storage, the storage is still decreasing. Am I correct? If so, is there a way to also move dalvik cache to the ext partition - I had it like this on MIUI & never looked at available memory ever again.
First of all, have you really partitioned your SD card? Make sure you followed the 3rd step on this guide: http://www.mrmuh.com/2012/01/update-a-motorola-milestone-from-motorola-firmware-to-cyanogenmod-7/ . You should have your SD Card partitioned with two partitions, the first should be FAT32 that's used normally on Android, and the second EXT3 or EXT4. Obviously, make sure you have a backup of your FAT32 partition before partitioning.
Second, you should understand how the apps2ext scripts on CM7 work. Application installs that would be stored on internal memory are rerouted to the EXT3/4 partition on the SDCard. This happens at the underlying system (linux) level, Android (that runs on top of linux) is not aware of this rerouting, so, as far as Android "knows", apps that are rerouted to the EXT partition are on the phone's internal memory. That means that you should make sure that apps you need installed on the EXT partition of the SD card are shown in "Applications > Manage applications" list to be installed on the internal memory. Yep, it's confusing, but once you understand how it works and why it works that way, it makes sense.
Third, the fact that apps are rerouted to the EXT partition doesn't mean that everything about the app will live on the ext partition: it means only the main application package will live on the ext partition, application data is still stored on the internal memory. For most apps, the amount of data used for application data are much smaller than the application package, but in some apps the amount of application data from the app may often surpass the size of the app itself - for example, in my phone, Tweekdeck stores about 9Mb of data, which is about 10 times the size of the application itself (820kb) - presumably this amount of data is cached tweets, pictures, etc. But that case is usually the exception, not the rule, I've just mentioned it so you understand that using apps2ext doesn't mean your internal memory will always stay unused, it just means it will be used (way) less.
Finally, regarding the CyanogenMod Settings location setting, if you understood what I said above, you should now understand that it should actually be set to always install to "Internal", rather than external. However, there's a bug in this that you should be advised, that not all apps will respect this setting: some apps will install to external regardless of how you've configured that setting (meaning the app will use Froyo/Gingerbread native Apps2SD, hence being installed to the FAT partition of the SDCard). So, when you install a new app, check on app management if it didn't get installed to the SDCard, and move it to the internal memory if that's the case. For these kind of apps, you'll have to do it every time you update the app too.
Thanks, I edited my previos post..
I actually have 3 partitions, a FAT32, an ext2 (maybe it's ext3, but doubt it - partitioned some months ago, so my memory's hazy), and a SWAP - which I should get rid of, but am too lazy.
I understand entirely what you've said, I know that internal is really ext if working, and sd is FAT32 partition.
You see, I'm just new to this rom and have to trial and error until I understand, with miui you just flashed the rom and the a2sd scripts and didn't bother again (maybe only to move an app that installed to FAT partition). But it seems CM7 is simply just to flash the rom and you're good to go. But as I was pondering in my previous post...is there any way to move dalvik cache to ext?
Thanks for putting up with me..I'm almost there.
Sent from my Milestone using Tapatalk
d.casper.b said:
Thanks, I edited my previos post..
I actually have 3 partitions, a FAT32, an ext2 (maybe it's ext3, but doubt it - partitioned some months ago, so my memory's hazy), and a SWAP - which I should get rid of, but am too lazy.
I understand entirely what you've said, I know that internal is really ext if working, and sd is FAT32 partition.
You see, I'm just new to this rom and have to trial and error until I understand, with miui you just flashed the rom and the a2sd scripts and didn't bother again (maybe only to move an app that installed to FAT partition). But it seems CM7 is simply just to flash the rom and you're good to go. But as I was pondering in my previous post...is there any way to move dalvik cache to ext?
Thanks for putting up with me..I'm almost there.
Sent from my Milestone using Tapatalk
Click to expand...
Click to collapse
in the market you will find an app called s2e which moves app data, davlik cache to sd
also link2sd also free's up more space and makes cm7 snappier
please don't install such things to CM7 for Milestone unless you know what you are doing and you are able to resolve conflicts with the existing scripts
dalvik-cache is already moved automatically
if you want to free more space in /data, enable lib2ext to move native libraries to ext - it's mentioned in the changelog for 7.1.2 release
app data itself should not be moved as it can cause instability
d.casper.b said:
Thanks, I edited my previos post..
I actually have 3 partitions, a FAT32, an ext2 (maybe it's ext3, but doubt it - partitioned some months ago, so my memory's hazy), and a SWAP - which I should get rid of, but am too lazy.
Click to expand...
Click to collapse
Yeah, get rid of swap, there won't be any use for it (for now anyway) and it's best for you at this point to have a known working structure (two partitions, 1st FAT, 2nd ext3/4) for your SD as you're troubleshooting your problems/questions, it'll make it easier for us too as this will eliminate potential points of failure or inconsistencies. And you should really consider upgrading to a journaled filesystem, either ext3 or ext4. Using ext2 is unreliable because Android doesn't umount the ext partition cleanly on reboot or shutdown, so you may have problems with apps disappearing or misbehaving every other reboot. Using ext3/4 with journal elimitates this problem since the journal is just replayed for the uncleanly umounted partition and the filesystems behaves more consistently.
d.casper.b said:
You see, I'm just new to this rom and have to trial and error until I understand, with miui you just flashed the rom and the a2sd scripts and didn't bother again (maybe only to move an app that installed to FAT partition). But it seems CM7 is simply just to flash the rom and you're good to go. But as I was pondering in my previous post...is there any way to move dalvik cache to ext?
Click to expand...
Click to collapse
The apps2ext script built on CM7 should do this by default - you probably already have your dalvik-cache on the ext partition. To check this, go into OR, enter the console and type: "ls /sddata/dalvik-cache" . If it returns a list of files, you've already got the dalvik-cache on your ext partition. Another option is setting the option dalvik.vm.dexopt-cache-only to 1 in the file /system/build.prop . This will put all dalvik-caches (both from user apps and system apps) on the phone's internal cache partition, thus still freeing space on the internal memory but without using the ext partition, but that's not recommended if you install too many apps because the cache partition may run out space and that will spawn all kinds of weird behavior on Android. The safer route is just using the default configuration anyway (user apps dalvik-cache on sd-ext).
Another option to further reduce internal memory use is using lib2ext, that will move user apps native libraries to the ext partition, but the memory gain in this case is dependent on which apps you use and how big their native libraries (if they even have one) are. To activate it, just go into the Terminal app (with Android booted) and type:
$ su
# lib2ext
And reboot. The libraries will be moved to the ext partition during boot. Make sure you have a big enough ext partition to hold everything (apps, dalvik-cache and apps libs) - the size to recommend is very dependent on how many apps you use and how big they are, but I'd say 512Mb would be the bare minimum.
in the market you will find an app called s2e which moves app data, davlik cache to sd
also link2sd also free's up more space and makes cm7 snappier
Click to expand...
Click to collapse
DON'T! JUST DON'T! These third-party apps will cause all kinds of problems with CM7 builtin apps2ext.
EDIT: Oh well, Kabaldan already put all my rambling much more succintly than I could... I'm way too talky
well i was jus trying to help.. .anyway guys thanks i guess i won't be needing those apps anymore ...sorry for my noobness
Thank you so much guys!
It seems like it's working. I will check out lib2ext & the other suggestions tonight or over the weekend (on my way to work now).
I must say, I thought the move to CM7 would be a temporary one, but the speed gain is just what I needed, & the tweaks I thought I'd miss I am finding hidden in the settings .
Just wondering on the battery now - but I've been fiddling non-stop.
So let me play a bit more the weekend & I'll merge my ext2 and SWAP partition into one ext3 partition.
Thanks all, and kabaldan for your hard work on this rom.
Sent from my Milestone using Tapatalk
Just as I was on my way...
Everything's running fine, A2SD works. But now, I partitioned my SD card with a 2nd partition (ext3, it was ext2), but now widgets are not loading. Checked the apps install location, and it's 'internal', ie. ext3. I never had this before. I think maybe it's due to the filesystem now?
EDIT: Ok, ext2 is doing the same. I can't keep starting from scratch the whole time guys.
EDIT2: It's now suddenly working! Just have a Fat32 and an Ext3 partition. But I don't understand because it's been setup like this twice before with no success. I'll hold thumbs!
PS, CyanogenMod is quite up my alley now, speed is awesome and I'm happy.
Sent from my Milestone using Tapatalk
Hi There
Can someone explain what he\she did to partition SD card, and make all apps get installed on it.
Please note :
1. I don't want to use Titanium backup for this usage. I don't have the paid version and I'm tired of doing this one app at a time.
2. I saw some guides on the net, but they were all for GB.
(partition the microSD on PC using minitool) -can we use ext4 on our MTD ROMs ? What is the 1st partition for ? and the 2nd ?
(install busybox and super user) - Is it still needed ? (MIUI for example has LBE as su).
(install Link2SD) - Is it always in memory ?
(reboot and put partitioned SD card)
(Define Link2SD)
3. I also saw swapper instructions but I can manage with 170MB free RAM memory I get after removing all unnecessary system apps, and I remember ppl saying then that it kills the SDCard very quickly.
If someone has a clear guide or instructions that he knows work, that will be nice.
Thanks in advance.
Step 1. Partition your SD card to have a sd-ext partition. This can definitely be ext2 or FAT16. Anything else depends on your kernel. Most of them do support ext3 and 4, but... start with something fairly basic.
Regarding recoveries:
TWRP has always failed for me on this, so I'd avoid that.
This may be doable in CWM. I've seen reference to that newer versions of CWM removed the partition option, so you might need to flash an ICS ROM with an older kernel, repartition, and then flash back to the one you want.
Also note that if you use CWM to repartition, your SD-card will be wiped. So do a backup first.
Step 2. Install Mounts2SD. Either from XDA or the Play Store. Even if you do take it from the Play Store to get update notifications, I highly suggest grabbing the recovery script from the XDA thread so that you can get back your shifted applications without needing to re-download and install M2SD, since it likes to be on internal which means... shifted off.
Step 3. Open Mounts2SD. Grant SU rights at whatever point it asks for it during step 3. Hit the menu button. Go to Application Settings. Install the Startup Script. Tell it to use the built-in busybox as well, so that you don't need to install anything or worry about it failing. Back out of the Application Settings.
Step 4. Press on the Wrench to go into the actual specific settings. I currently have forced Cache, 1% Storage Threshold, Applications are the only bit moved, the File System Check is on and using the Ext4 Driver, 128KB Deadline for Internal and 4096 with Deadline for External, and Safe Mode is disabled. But decide on what you want yourself, set it, go back to the Eye to see your current info.
Step 5. Reboot.
Step 6. Wait 1-30 minutes for it to finish moving all your stuff around.
Step 7. Unlock your phone, open Mounts2SD, and make sure everything looks pretty on that first 'Eye' info tab. If you like it then close Mounts2SD and keep going on your merry way. If you don't like it or you've done something like offload your data and now your phone is wretchedly slow, go to the Wrench, change your settings, go back to the Eye, and reboot again. Repeat until satisfied.
I thought it would be simplier.
A few more questions:
1. If I partition SD on PC, then I don't need any partitioning on recovery so it should work fine even on TWRP or advanced CWMs. Am I right?
2. Why do I need scripts for? Isn't the app enough?
3. Why should/could it possibly slow down my device? TB 'move to SD' for all doesn't slow my device what so ever.
4. How and where do I see what partition is used for what?
5. How much RAM does the app take?
6. Have you tried other apps link2sd or something CM has built in I think.?
Thanks.
sent from me
New answers to new questions.
1. Skip step 1 if you've done it on your PC. I just suggested recovery as that's easy... if you've made your sd-ext partition on the PC, step 1 is done.
2. No clue on Link2SD. I use Mounts2SD instead since it lets me set things. It probably does the same thing though and sets a init.d script that gets run during startup.
3. True. For some reason though having all your data moved to sd-ext makes our phone go to a crawl. Same if you move off the dalvik.
4. That's in Mounts2SD. No clue how you can see if you're using Link2SD.
5. For Mounts2SD, none while it's being used, since it just runs as a startup script. The app is just to control the script.
6. Not successfully. I had tried 5 or 6 different apps back a year ago or so when I first started playing with sd-ext and Mounts2SD was the best and free, so... never looked back after that. Now you can also do some system-flag tweaking if you want to donate, but the sd-ext stuff is all free.
I was able to successfully partition SD and use mount2sd on 4.3 SlimBean.
however, it was rather slow.
CM 10.1 and CM10.2 by DJL. did not allow me to partition nor did they recognize SlimBean's partition even if I replaced them kernel (to NilTMT).
I'm currently using CM10.1 which is stable as a daily driver and manually swapping apps with TB, I hate it, but this is the best combination I've come so far.
I sold my wife's SGS4G and upgraded her to SGS3 and hopefully in a year I will do the same. it had its moments, but on the bottom line it's a pretty ****ty phone with its lack of internal mem...but hey, it drove so many of us to go deeper and deeper trying to understand and made us more tecnolgical and solution oriented.
Mounts2SD worked for me on CM10.1, so not sure why it failed for you. Ah well.
A few things I have found...
Yes, you can partition on Windows, but you're really asking for trouble. It's not too bad download Ubuntu or the like and you can boot off a USB stick without touching your Windows install.
The TeamAcid kernels that I know of handle ext2/3/4 file systems. All kinds of arguments as to which are better. I personally use ext4 and don't find it obviously "slow" for the way I use my phone.
That said, what the boot scripts (which are part of a flashed "kernel" for the SGS4G) actually do with a "special" partition is another story. In some cases the first stages of booting will look for special partitions and mount them in pre-configured places. For example, the second partition of the removable card might be mounted on /sd-ext/ in many CyanogenMod ROMs. Many (most?) SGS4G ROMs don't have these "special" mount rules defined.
Moving an app to SD using the "native" approach just moves the app and none of its data to the SD card. It won't for example, move 25 MB of mail from /data/data to your microSD
Moving an app to SD (or anywhere else) doesn't keep it from generating its classes in /data/dalvik-cache -- It isn't "free" to have an app on SD as far as internal storage goes, even if it doesn't write any data.
Moving an app to SD will absolutely slow down your boot time. It does it by creating a file that contains a file system that then gets read and mounted at boot time. You can watch the parade of them getting mounted using adb logcat. It can take a minute or two to mount them all. Once mounted, that double layer of file systems shouldn't slow you down too much, since it is basically a read-only kind of thing.
Scripts are required since you need to be able to "fake out" the operating system as to where things are stored for anything (except if you just use the native app to SD method). In most cases you need new partitions mounted before the Android part of the OS starts running.
Some scripts are more robust than others.
TitaniumBackup (paid version) has a way to move data to an external partition. It works like a charm for me (64 GB Sandisk UHS-1 / Class 10 microSD). It was very tweaky for me to get it to recognize the ext4 partition the first time. It can bulk-move app data to the partition. I don't know which, if any, of the other scripts move the data to an external partition.
On my phone, an ext4 file system can be significantly faster than the internal yaffs, especially for write. Alas, it usually seems to be read that is a killer for most things in an well-written app. On my phone, yaffs can be faster than ext4 for short reads. Who knows how this would play out in real-world usage.
Other things that TitaniumBackup can do that help free up internal storage, at least in the paid version, are:
Dalvik cache cleanup
Integrate system Dalvik cache into ROM
Integrate update into ROM
Convert to system app
I can confirm Link2SD works where Mount2SD fails, which is an ext3 partitioned sd-ext on AOKP. it doesn't get any simpler than that.
sent from me
Hello.
I guess the following is an almost general CM problem at low ROM space. That's why I post it here...
Is there any reason why I cannot install as many apps as the internal memory allows me with enough space?
It is about Xperia 2011 (still 512 MB ROM internal memory):
CM12: Regular 512MB ROM is 'expanded' by a separate ext3 or ext 4 partition on SD card.
CM13..14: No extra partition is necessary.
The following experience I made with any of the versions CM12 to CM14 (e.g. on Sony Xperia Ray or Neo):
The more apps I installed the longer I had to wait for the completion. The same with deinstallations!
Even after the complete and successful download in GooglePlay it then needs several minutes until the progress bar changes to "app is been installed", independent from the installed app. What can be the reason for that phenomena?
This experience may have made everybody having this constellation cause it appeared here very reliable at any CM version!
However, I thought I could live with that. But after I installed about 15 own apps the launcher (here: Trebouchet) crashed directly after I installed the 16th app. When I uninstalled it the system runs stable again.
I attached to this messages the related CM12 bug report. Can this help you?
Also strange: The Android storage management says the following about the internal memory:
* Complete space: 6,63 GB
* Available: 3,70 GB
* Apps: 1,66 GB
* Cache data: 174 MB
Where is the remaining space of 1,1 GB then?...
So who could give an explanation...
1) why the installation/deinstallation time systematically increases (up to 10 minutes and more) with the increasing number of installed apps?
2) why there is a limited number of apps I am allowed to install? (there is still enough space on my 6 GB ext3 F2FS partition left!)
3) how I can solve both problems but especially avoid the launcher crash?
Thank you so much for your help!
Hello to all of you,
I would be happy already if someone of you would report about his/her experiences (with comparable conditions) and inform me if my problem is usual/known or an exception!
MANY thanks for that!
Hello
i would like you to provide a logcat, as for what i assume is it maybe a internal storage problem, maybe faked or something, a logcat and some screenshots would be helpful.
Logcat of Trebouchet crash for analysis
Hello Hope,
in the meantime I totally reinstalled CM 12.1. I even used another sd card (also Class 10).
And this time I even did not install many apps until the strange Trebouchet crash appeared. So the installation was pretty new. Just 5 minutes after installation the system was unstable already!!
Unbelievable how unstable CM12..14 are here.
Note: If you go into the safe mode this problem does not exist!!
Attached you will find the necessary logcat now which contains a Trebouchet crash. I filtered it so that only warnings and occasions with higher priority are contained.
Will you find the problem now?...
I am keen to get your analysis.
Thank you very much.