My dalvik-cache is In sd.
Thanks man!
Thanks man!
Last question. After flashing new nightly and script, rebooting takes long time?
Wont it say insufficient space?Yep,s sure does take awhile. what I do is wipe cache and dalvik cache, flash rom, kernel, DTa2sd 2.7.5.2, reboot. Then go to terminal emulator and run a2sd cachesd, phone reboots and all is well.
Found the problem all well now. Tested reflashing and reflashing. All's good. Thanks for the assistance.
I use the modified darktremor script that remove 05mountsd in cm6 nightly rom. That solved my problem.Temasek, what was the problem and solution? Just in case others run into it..
I use the modified darktremor script that remove 05mountsd in cm6 nightly rom. That solved my problem.
Yep,s sure does take awhile. what I do is wipe cache and dalvik cache, flash rom, kernel, DTa2sd 2.7.5.2, reboot. Then go to terminal emulator and run a2sd cachesd, phone reboots and all is well.
I tested reflashing my rom using nightly builds 5 times over. With the modified script that remove 05mountsd file flashed each time, I had no issues. No wiping required and no redo of cachesd or any bootlooping.Since I use recovery Amon_Ra 2.0 I haven't to run a2sd cachesd every time I flash rom and DT.
I have dalvik-cache in sd. Before that recovery I had to run a2sd cachesd every time, but now dalvik-cache remains in sd.
I use the options "wipe only cache" and "wipe only dalvik-cache" on recovery.
I tested reflashing my rom using nightly builds 5 times over. With the modified script that remove 05mountsd file flashed each time, I had no issues. No wiping required and no redo of cachesd or any bootlooping.
That modified script helped in preventing problems in CM6.1 nightly builds.
Yes I tested 5 times. Each time I flash the modified script after flash rom. Only done cachesd one time. No wiping of caches. Btw I am also using dalvik-cache to sd.umm..interesting. I've never used the modded script and have the 05mountsd file in system/init.d also but its never caused a problem. However, if I can use it once and not have to move dalvik-cache for every nightly that would be great.
Temasek, I already have DT 2.7.5.2 running with dalvik-cache moved to cachesd(sd-ext partition). To set it up, you still have to flash after each nightly but you don't have to run a2sd cachesd after the first time, right?
Yes I tested 5 times. Each time I flash the modified script after flash rom. Only done cachesd one time. No wiping of caches. Btw I am also using dalvik-cache to sd.
That modified file was unsigned though. I will sign it when I go to my pc later. More for convenience purpose. Thanks to the original poster that added a line in the script to remove 05mountsd. This I believe more for cm6 build roms.
Anyway heres the modified script, resigned by myself. - Saves me 2 clicks in RA RecoveryNot a problem, thanks for the info. I'm using RA v1.8.0 which I think can flash unsigned zips. Will try after tonight's nightly.
btw, saw the ADW update to 1.3.1 were submitted to gerrit today but not merged yet.
Anyway heres the modified script, resigned by myself. - Saves me 2 clicks in RA Recovery
By default amon ra recovery 2.0 uses signed zips. To flash unsigned u have to click "others" then click "unsigned....blar......blar"What two clicks is that? BTW thanks for the tip.
Sent from my Nexus One using XDA App
Anyway heres the modified script, resigned by myself. - Saves me 2 clicks in RA Recovery
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.)
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.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.
su
tune2fs -o journal_data_writeback /dev/block/mmcblk0p2
If I had figured it out, than why i had asked here.
I will be thankfull if u can guide me
thanks in adv.
Hi,
I've 2 questions:
1. I have a HTC Desire GSM that's running CM 7.0.3 and I've run the DT A2SD script to put my apps and dalvik-cache to the EXT partition on the sdcard. I wish to update to CM 7.10, and the instructions seem straightforward enough (nandroid, flash, that's it). I'm wondering if I need to do anything about A2SD for the update?
2. I wish to upgrade to a larger sdcard. How can I migrate from my existing sdcard to a new one?
do i get these problems bcoz im on stock kernel??
so far no1 wants to help me..