[Script][A2SD]Darktremor 2.7.5.3 Beta 04 [Desire] (01/29/2011)

Search This thread
By:
Advanced…
T

tkirton

Senior Member
Jul 13, 2009
2,044
224
51
Katy Texas
www.darktremor.info
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:Darktremor1@ftp.darktremor.info (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.
 
Last edited:
  • Like
Reactions: bishwa_it, exitmood, sanjmur and 1 other person
T

tkirton

Senior Member
Jul 13, 2009
2,044
224
51
Katy Texas
www.darktremor.info
Last edited:
T

tkirton

Senior Member
Jul 13, 2009
2,044
224
51
Katy Texas
www.darktremor.info
I don't have any roms using it in Desire...hence why I'm posting this. But:

Kurt666
- For testing on Pay's ROM for Desire v1.4 (HTC Desire)
​
Click to expand...
Click to collapse


So there is one rom that is tested with it.



I've checked a good segment of the roms here, and it should work just fine, especially the 2.7.5 version (as the swap, dalvik-cache and the applications are all separate functions now).


I'm trying to expand the program's scope. I have six different platforms that run it (21 roms total) and I have one Desire rom tested...but none actually using it (my fault...should've expanded this a month ago).



Nekromantik said:
Desire aint listed??
Click to expand...
Click to collapse
 
G

gatsu_1981

Senior Member
Jan 4, 2009
456
15
nerd-tech.it
Backing up just now my Open Desire 1.5 on nandroid.
Going to be your guinea pig for Open Desire (AOSP) ;)

I will paste the logcat output of my first boot (if there will be any) :D
 
Last edited:
antz88c

antz88c

Senior Member
Mar 9, 2010
435
46
Will try to test on modaco r3.1, wish me luck :)

Sent from my HTC Desire using Tapatalk
 
G

gatsu_1981

Senior Member
Jan 4, 2009
456
15
nerd-tech.it
antz88c said:
So it didn't work?

Sent from my HTC Desire using Tapatalk
Click to expand...
Click to collapse

It booted in the same time that it booted without applying the tremor script, and I think that the logcat was quite similar too.
And the free space reported is the same than before.

So, it didn't work, or it was already working before :D

EDIT:

I decompressed the script inside OSx, and I looked inside folders.
Well, it seems that the script didn't run at all, since I have no "a2sd" neither "app2sd" on my /system/bin.

REEDIT:

I ran it again, now it seems that it actually ran.
I will provide my new pastebin later :D
 
Last edited:
antz88c

antz88c

Senior Member
Mar 9, 2010
435
46
Boot loop only here, nandroid back to my previous ROM.

Sent from my HTC Desire using Tapatalk
 
StuMcBill

StuMcBill

Senior Member
Feb 13, 2010
1,895
120
This sounds very interesting, and I would like to try and help when I can, which probably won't be for a couple of days.

But........for when that day comes.......how do I do a logcat?

Sorry, I am still relatively new to the whole Android thing.
 
bradputt

bradputt

Senior Member
Jun 16, 2010
1,336
296
StuMcBill said:
This sounds very interesting, and I would like to try and help when I can, which probably won't be for a couple of days.

But........for when that day comes.......how do I do a logcat?

Sorry, I am still relatively new to the whole Android thing.
Click to expand...
Click to collapse

yes, i got a bootloop on defrost 1.8.

how to do a logcat?
 
G

gatsu_1981

Senior Member
Jan 4, 2009
456
15
nerd-tech.it
bradputt said:
yes, i got a bootloop on defrost 1.8.

how to do a logcat?
Click to expand...
Click to collapse

decompress android sdk (check on google for the sdk package, is quite small), then go inside the "tools" folder (I assume you have already your drivers installed).

then go on command prompt, and

Code: 
adb logcat
will show the logcat.
Code: 
adb logcat > bootlog.txt
will create the boot log (you won't actually see anything on screen since the output is redirected on the txt file.

You can:

start your phone
type adb logcat

CTRL+C when the phone is booted.
It will automatically stop if a reset occurs.

Then you go on pastebin (search on google) and paste the txt inside the pastebin.
And you can provide here simply the pastebin url that you can find after the submit button.
 
T

tkirton

Senior Member
Jul 13, 2009
2,044
224
51
Katy Texas
www.darktremor.info
Last time I saw that message, root wasn't working correctly. At least it wasn't working correctly on my phone.

Is there something different relating to root on these phones? Does the boot sequence have root access to /system (or is this phone have nand protection on it? I know the Evo has that but can be circumvented).

That part is just a piece that moves other apps2sd/dalvik-cache/zipalign programs so they don't interfere...the 2.7.5 Preview Fix 2 also removes those files during the flashing process, so that part really is only a failsafe.

The main program comes after that part (04apps2sd for busybox run-parts, a2sd for direct run).

gatsu_1981 said:
http://pastebin.com/mx3PsHwZ

First run, then I got a reset. Then it reset-loop. With the same message.
Sorry man, it isn't quite ready for AOSP it seems :(

Those are a couple of after-install output, it doesn't do much though.
http://pastebin.com/ZVx5svQj
Click to expand...
Click to collapse
 
T

tkirton

Senior Member
Jul 13, 2009
2,044
224
51
Katy Texas
www.darktremor.info
The important piece is the part after the realignment program...the one that starts with:

[*] Starting Darktremor Apps2SD version 2.7.5 preview fix 1

The lines after that one is the Apps2SD portion.

gatsu_1981 said:
http://pastebin.com/mx3PsHwZ

First run, then I got a reset. Then it reset-loop. With the same message.
Sorry man, it isn't quite ready for AOSP it seems :(

Those are a couple of after-install output, it doesn't do much though.
http://pastebin.com/ZVx5svQj
Click to expand...
Click to collapse
 
G

gatsu_1981

Senior Member
Jan 4, 2009
456
15
nerd-tech.it
tkirton said:
The important piece is the part after the realignment program...the one that starts with:

[*] Starting Darktremor Apps2SD version 2.7.5 preview fix 1

The lines after that one is the Apps2SD portion.
Click to expand...
Click to collapse

I can't understand what you mean.
Do you need some other line from adb logcat output? Since there is no more lines after the * line :D it just keeps resetting.
Or are you telling that it's installed? If so, why it keeps resetting our phone on froyo? :D

If I can help please send more flashable version or update this thread, I already have my nandroid so testing it for you will be very quick.
 
Last edited:
You must log in or register to reply here.

Similar threads

S
[BETA 0.18.2.1][17.09] ICS for Desire[ALL HBOOTS][4.0.4]
Replies
17K
Views
7M
Saf98
Saf98
xavierjohn22
  • Poll
[ROM][MIUI-XJ] Mar 31 - 2.3.30 GB 2.3.7 EN-MULT+OTA+CM+Updater|D2EXT X-PART|A2SD+|D2W
Replies
19K
Views
4M
rmg2
rmg2
robocik
[ROM][New Sense][02 apr]RCMixHD v3.6, DATA++/D2EXT/A2SD+, Rotating or DeSensenized
Replies
13K
Views
3M
Arap01
Arap01
Mr.Mefisto
HTC Desire (Bravo) Index - Everything Desire is here! [24th/January/2015]
Replies
395
Views
4M
R
Rynpcfc
Sebby
  • Locked
[Discontinued]Runnymede AIO V6.1.1 Special Edition with INT2SD support [Beta]
Replies
18K
Views
4M
TonyStark R.I.P.
TonyStark R.I.P.

Top Liked Posts

24 Hours All time
  • There are no posts matching your filters.
  • 4
    T
    tkirton
    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:Darktremor1@ftp.darktremor.info (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.
    View
    1
    T
    tkirton
    Do me a favor...send me the /data/dta2sd.log, /data/dta2sd.lg1 and /data/dta2sd.lg2 files to rtkirton@gmail.com.

    The thing that is wrong with this picture is that the data says it is moving, but it doesn't look like it is...so something has gone wrong.

    After you capture the logs, you can type a2sd remove to get out of the boot loop temporarily (it will move apps to internal storage). Once you reboot, type a2sd reinstall and see if that helps.

    UPDATE: Found the issue. The rom developer is using oxygen.filesystem.ready to release the init.rc. CyanogenMod in its earlier years and DamageControl does the same thing. I'll add it and give you an update.

    Xinot said:
    Oxygen v2.0 RC7.
    Stuck in HTC logo.

    Code: 
    * daemon started successfully *
--------- beginning of /dev/log/main
I//system/xbin/busybox(   71): [ ] Apps2SD is launching...
I//system/xbin/busybox(   71):  __ _____
I//system/xbin/busybox(   71): |  \  |  
I//system/xbin/busybox(   71): |   | |  
I//system/xbin/busybox(   71): |__/  |  Darktremor Apps2SD 2.7.5.3 Beta 2 (2011-01-22)
I//system/xbin/busybox(   71): [ ] Startup Boot Sequence
I//system/xbin/busybox(   71): [ ] GetProp Command = /system/bin/toolbox getprop
I//system/xbin/busybox(   71): [ ] SetProp Command = /system/bin/toolbox setprop
I//system/xbin/busybox(   71): [ ] Mount Point = /sd-ext
I//system/xbin/busybox(   71): [ ] Checking for existence of Dalvik Heap Change Program.
I//system/xbin/busybox(   71): [!] Dalvik Heap Change Program Not Found.
I//system/xbin/busybox(   71): [ ] Creating /cache/dc
I//system/xbin/busybox(   71): [ ] Symlinking /cache/dalvik-cache to /data/dalvik-cache
I//system/xbin/busybox(   71): [ ] Starting Darktremor Apps2SD Version 2.7.5.3 Beta 2
I//system/xbin/busybox(   71): [ ] Listing /proc/filesystems
I//system/xbin/busybox(   71): /proc/filesystems
I//system/xbin/busybox(   71): [ ] Directory Listing of /dev/block
I//system/xbin/busybox(   71): brw-------    1 root     root        7,   0 Jan 24 09:51 /dev/block/loop0
I//system/xbin/busybox(   71): brw-------    1 root     root        7,   1 Jan 24 09:51 /dev/block/loop1
I//system/xbin/busybox(   71): brw-------    1 root     root        7,   2 Jan 24 09:51 /dev/block/loop2
I//system/xbin/busybox(   71): brw-------    1 root     root        7,   3 Jan 24 09:51 /dev/block/loop3
I//system/xbin/busybox(   71): brw-------    1 root     root        7,   4 Jan 24 09:51 /dev/block/loop4
I//system/xbin/busybox(   71): brw-------    1 root     root        7,   5 Jan 24 09:51 /dev/block/loop5
I//system/xbin/busybox(   71): brw-------    1 root     root        7,   6 Jan 24 09:51 /dev/block/loop6
I//system/xbin/busybox(   71): brw-------    1 root     root        7,   7 Jan 24 09:51 /dev/block/loop7
I//system/xbin/busybox(   71): brw-------    1 root     root      179,   0 Jan 24 09:51 /dev/block/mmcblk0
I//system/xbin/busybox(   71): brw-------    1 root     root      179,   1 Jan 24 09:51 /dev/block/mmcblk0p1
I//system/xbin/busybox(   71): brw-------    1 root     root      179,   2 Jan 24 09:51 /dev/block/mmcblk0p2
I//system/xbin/busybox(   71): brw-------    1 root     root       31,   0 Jan 24 09:51 /dev/block/mtdblock0
I//system/xbin/busybox(   71): brw-------    1 root     root       31,   1 Jan 24 09:51 /dev/block/mtdblock1
I//system/xbin/busybox(   71): brw-------    1 root     root       31,   2 Jan 24 09:51 /dev/block/mtdblock2
I//system/xbin/busybox(   71): brw-------    1 root     root       31,   3 Jan 24 09:51 /dev/block/mtdblock3
I//system/xbin/busybox(   71): brw-------    1 root     root       31,   4 Jan 24 09:51 /dev/block/mtdblock4
I//system/xbin/busybox(   71): brw-------    1 root     root       31,   5 Jan 24 09:51 /dev/block/mtdblock5
I//system/xbin/busybox(   71): /dev/block/platform:
I//system/xbin/busybox(   71): drwxr-xr-x    3 root     root           120 Jan 24 09:51 msm_sdcc.2
I//system/xbin/busybox(   71): [ ] Listing of partitions on /dev/block/mmcblk0
I//system/xbin/busybox(   71): Disk /dev/block/mmcblk0: 7948 MB, 7948206080 bytes
I//system/xbin/busybox(   71): 4 heads, 16 sectors/track, 242560 cylinders
I//system/xbin/busybox(   71): Units = cylinders of 64 * 512 = 32768 bytes
I//system/xbin/busybox(   71):               Device Boot      Start         End      Blocks  Id System
I//system/xbin/busybox(   71): /dev/block/mmcblk0p1             129      209792     6709248   b Win95 FAT32
I//system/xbin/busybox(   71): Partition 1 does not end on cylinder boundary
I//system/xbin/busybox(   71): /dev/block/mmcblk0p2          209793      242560     1048576  83 Linux
I//system/xbin/busybox(   71): Partition 2 does not end on cylinder boundary
I//system/xbin/busybox(   71): [ ] EXT partition found at /dev/block/mmcblk0p2.
I//system/xbin/busybox(   71): [ ] Checking volume /dev/block/mmcblk0p2.
I//system/xbin/busybox(   71): [ ] Attempting to mount /dev/block/mmcblk0p2.
I//system/xbin/busybox(   71): [ ] Mount returned code: 0
I//system/xbin/busybox(   71): [ ] Mount successful: /dev/block/mmcblk0p2
I//system/xbin/busybox(   71): [ ] Checking for directory structure.
I//system/xbin/busybox(   71): [ ] Creating /dalvik-cache
I//system/xbin/busybox(   71): [ ] Creating /sd-ext/data
I//system/xbin/busybox(   71): [X] No swap partitions found on /dev/block/mmcblk0
I//system/xbin/busybox(   71): [ ] Heap Size set to: 32m
I//system/xbin/busybox(   71): [ ] Realigning /data/app to /sd-ext/app
I//system/xbin/busybox(   71): [ ] Realigning /data/app-private to /sd-ext/app-private
I//system/xbin/busybox(   71): [ ] Checking for previous version flag files...
I//system/xbin/busybox(   71): [ ] Applications are stored 
I//system/xbin/busybox(   71):     in /data/app
I//system/xbin/busybox(   71): [ ] Private Applications are 
I//system/xbin/busybox(   71):     stored in /data/app-private
I//system/xbin/busybox(   71): [ ] Dalvik-Cache is located in /data/dalvik-cache
I//system/xbin/busybox(   71): [ ] Program Data is 
I//system/xbin/busybox(   71):     stored in /data/data
I//system/xbin/busybox(   71): [*] Darktremor Apps2SD 2.7.5.3 Beta 2 active.
I//system/xbin/busybox(   71): [!] ZipAlign flag file not detected.
I//system/xbin/busybox(   71):     Will not perform ZipAlign
I//system/xbin/busybox(   71): [ ] Setting File System Ready property to 1.
I/logwrapper(   71): /system/xbin/busybox terminated by exit(0)
    Click to expand...
    Click to collapse
    View
    1
    T
    tkirton
    1. The error you got is a bug in the program. I fixed it and will release a new version today (Beta 3...there's enough fixes to warrant it).
    2. The space will continue to decrease as your program data and caches (which are located in /data/data) is on your internal storage. Depending on what you are doing in regards to phone activity and the type of programs you are installing, it can appear to decrease significantly.

    A couple of options you can take:
    1. Look for a cache cleanup program such as CacheMate that will clean up the other caches such as browser cache.
    2. You could try the experimental function of 2.7.5.3 and move /data/data to the SD card.

    [armitage] said:
    Think I got a little problem here aswell...
    Installed the latest version yesterday on my CM6 (last nightly) and in the beginning it moved all apps without a problem.I also moved dalvik and was up to 109mb free.After that I wanted to install a few more apps but now flash space kept on decreasing.I'm now down to 89mb.
    I mean did I misunderstand something here,is that the way it works or is there something wrong?
    Also I have an error massage when starting the a2sd check...
    Error:
    /system/bin/chka2sd: line 83: [: too many arguments

    Complete check:
    Code: 
    * daemon not running. starting it now on port 5037 *
* daemon started successfully *
[ ] Apps2SD is launching...
 __ _____
|  \  |
|   | |
|__/  |  Darktremor Apps2SD 2.7.5.3 Beta 2 (2011-01-22)

[ ] GetProp Command = /system/bin/toolbox getprop
[ ] SetProp Command = /system/bin/toolbox setprop
[ ] Mount Point = /sd-ext
[ ] Starting Apps2SD Check Program.
/system/bin/chka2sd: line 83: [: too many arguments

Darktremor 2.7.5.3 Beta 2 Apps2SD Status Report
================================================================================
===
Legend: [*]=Setting is correct
        [!]=Setting is correct, but not optimal.
        [X]=Setting is incorrect and needs to be fixed or option is not availabl
e.
================================================================================
===
Block Device            - [*] /dev/block/mmcblk0p2
Partition Type          - [*] EXT2
Mount Point             - [*] /sd-ext
Support EXT2?           - [*] Yes
Support EXT3?           - [*] Yes
Support EXT4?           - [*] Yes

Apps                    - [ ] Linked to SD Card.
                          [ ] No Apps2SD Flag File not found.
                          [*] Programs run from SD card
                              To run from internal storage, type a2sd remove

Private Apps            - [ ] Linked to SD Card.
                          [ ] No Apps2SD Flag File not found.
                          [*] Private Programs run from SD card
                              To run from internal storage, type a2sd remove

Dalvik Cache            - [ ] Symbolically Linked.
                          [ ] Dalvik to SD flag file found.
                          [*] Dalvik runs from SD card
                              To run from internal storage, type a2sd nocache
                              To run from /cache partition, type a2sd cachepart

Data                     - [*] Program Data on Internal Storage.
Swap                    - [ ] Partition not present or no swap support.
                          [*] Swap does not start.

ZipAlign                - [*] Not running at boot.
                          To activate it, type a2sd zipalign

Dalvik Heap(MB)         - [*] 32m

Low Memory
Killer Settings         - [*] 1536,2048,4096,5120,5632,6144
                          Note: Values are in pages.
                          1 page = 4KB memory.

                          Values represent the following:
                          1st number = Foreground App
                          2nd number = Visible App
                          3rd number = Secondary Server
                          4th number = Hidden App
                          5th number = Content Provider
                          6th number = Empty App
    Click to expand...
    Click to collapse
    View
    1
    T
    tkirton
    It's never done that to me...but I did find problems with the code that actually performed the move when you told it to go back to internal storage. I ended up rebuilding that section (all six dalvik-cache move commands) in Beta 03, so it should work better now.

    By default, dalvik-cache doesn't move from internal storage unless you tell it to.

    bakedecake said:
    I thought I had moved dalvik cache back to internal because the internal storage went down from 136 free to 128 but after a reboot it went back again so I did a nandroid restore, installed the latest nightly then ran the 2.7.5.2 script and everything is fine. I'll try beta 3 when I update to today's nightly. Does beta 3 put dalvik cache on the ext by default or was that the bug? Or is the bug that you can't move it back to internal? Surely few people would want it on the ext?

    Sent from my HTC Desire using XDA App
    Click to expand...
    Click to collapse
    View
    1
    T
    tkirton
    Dalvik-cache shouldn't be on the SD card by default.

    If it is and you don't want it, type a2sd nocache

    bakedecake said:
    I got this too but after a battery pull and restart it had still done the business but i don't want dalvik cache on the ext.
    Click to expand...
    Click to collapse
    View

New posts