yashsingh1/xdaforums huggingface dataset:
[EVO 4G Android Development] Jykinturah:
To be honest, I am quite new with Android development. I think I will look at some documentation and such before I begin experimenting. Maybe I should do an adb pull of /data/data and look at the stuff there.

If you don't mind, I may request for it later.
[EVO 4G Android Development] tkirton:
Sure. Not a problem.
[EVO 4G Android Development] freeza:
Hi, what is he best heap size to use?

Also, can I use apps2sd on the updated 1.47 rooted ROM based on the OTA simply by flashing?
[EVO 4G Android Development] tkirton:
Normally on the Hero (the one I use), the heap size is 16mb (a2sd smallheap). DamageControl uses a heap size of 24mb (a2sd largeheap), which seems to make dalvik-cache runs faster. I included a 32mb heap setting (a2sd jumboheap) that I thought would be perfect for the added memory of the Evo.

Honestly, I'm not sure which one is better. I personally can't tell the difference between them. I would experiment between them and see...but I'm not sure you'll get a noticeable difference unless you clear your dalvik-cache.

As for running Apps2SD on the updated 1.47 rooted rom...if it is a stock rom, it won't run. This is because the stock rom by itself does not have the necessary components to launch any version of Apps2SD (CyanogenMod, Darktremor, DamageControl). Myself and another developer injected the Apps2SD functions in our stock rom and released it (it was just a stock rom...no other modifications was done). So, someone would have to inject the Apps2SD functions into the stock rom.
[EVO 4G Android Development] dpilcher:
Partition Size

Just received my 16G (C6) SD card and was wondering if anyone had recommendations for initial sizing of the partitions? Originally did a 50/50 split, but second guessing myself.
[EVO 4G Android Development] tkirton:
I have 4GB, but that's a bit excessive. Try around 1-2GB for the ext and, depending if you want a swap partition, 32MB for swap. All the rest goes to FAT32.
[EVO 4G Android Development] tkirton:
Preview Fix 2 is out...more corrections to JIT (seems this one is hard to get my hands on).
[EVO 4G Android Development] dpilcher:
Thanks for the feedback. I moved to 3G, but will probably take that down to 1.5 (or almost 3 times the phone's internal system memory correct?) Don't think I will enable a swap, even though it's a C6 with protection elements on the card, don't want continual rw.
[EVO 4G Android Development] tkirton:
I have swap on mine and I don't see any ill effects.

But you have an Evo, which has twice the memory of the Hero. You probably would benefit without a swap file.
[EVO 4G Android Development] tkirton:
Guide to add Apps2SD to roms

I have added a guide on my main thread that shows you how to add Apps2SD support in roms that don't have it.

http://xdaforums.com/showthread.php?t=715116
[EVO 4G Android Development] tkirton:
Bump...Preview Fix 4 is out (yes, I skipped PF3...Desire users got that one).
[EVO 4G Android Development] pastert33:
I'm trying to get apps2SD to work with the DC ROM and I'm not seeing this partition selection. When I click on partition, a menu opens up that says a lot about mount and unmount. Also says something about format boot, system, data,cache, sd card, sd-ext. Any help would be appreciated!
[EVO 4G Android Development] brownmc77:
I know this is probley a stupid question but whats the benefit of this?speed? And if so, is it a big differnence? Thanks
[EVO 4G Android Development] tkirton:
Are you trying to get Darktremor Apps2SD to work or the one already included with DamageControl.

If it is Darktremor, the GUI setup in DamageControl is not compatible. You need to use the commands via Terminal or adb shell. Type a2sd help for a list of commands and a description of what they do.
[EVO 4G Android Development] tkirton:
The only benefit is that it will allow programs to stay in memory longer. It is a little faster, but not significant.

Most people don't even bother putting a swap partition.

Using a program like Autokiller, which adjusts the values of the built-in auto termination routine, would benefit you far better than swap.
[EVO 4G Android Development] tkirton:
I haven't tried Miui yet, but what happens if you try to install it using their kernel?

I guess I know what to make my next test platform.
[EVO 4G Android Development] NewZJ:
if you try and install darktremor to miui it won't boot as it's already setup for a2sd

edit, I would be happy to test for you, I already have a list of kernels that won't work with a2sd

I opened terminal and typed a2sd help, got this
[EVO 4G Android Development] -Protos:
Thanks for the instructons link. No offense meant, I am just an FB hater and don't like to go there.
[EVO 4G Android Development] tkirton:
Ah...I can certainly understand that. I don't like Facebook, either (can't stand the developers...I swear they're smoking something)...but Facebook does give me the most exposure for my program.

One day I'll get some time to build my Darktremor website (since I pay for it anyways), then there won't be a need for the Facebook part.
[EVO 4G Android Development] tkirton:
I checked the two flavors of Miui that I could find. The most recent one runs Darktremor 2.7.5.2 (the previous version), so an upgrade should work just fine.

The other version looks like it is dated 12/9 and runs Darktremor 2.7.5 RC3, which is also upgradable.

As soon as my batteries for my phone charge again, I'll run some tests on 2.7.5.3 Beta 3a/3b.
[EVO 4G Android Development] freeza:
Hi, I recently installed beta 02 (haven't tried beta 03 yet) on top of 2.7.5.2 and upon booting, the ext3 partition wasn't even recognized anymore by apps2sd, but I booted into my ROM just fine. Programs were gone though. Needless to say I had to nandroid restore... Should that have happened? Or is there anything I have to do after upgrading from 2.7.5.2?

Thanks!
[EVO 4G Android Development] NewZJ:
how do I upgrade the a2sd that miui comes with? is it possible? flashing new will just lock phone on splash screen
[EVO 4G Android Development] jpmaniac87:
I just flashed over Ava's rom and it says it wont mount... been using a2sd on other roms. What gives? I already tried repair ext partition in recovery
[EVO 4G Android Development] dcharleyultra:
Same here with Burnt droid ROM.

I had no issues with 2.7.5.2 and Nuggy's RLS1 ROM.

Edit: Can we still get 2.7.5.2?

Swyped from my Evo 4G using Tapatalk
[EVO 4G Android Development] NewZJ:
same here with avaz3 and 03beta, I have a 1gb partition but a check shows

any suggestions?
[EVO 4G Android Development] fixxxer2008:
can darktremor be ported to the epic at all?
[EVO 4G Android Development] tkirton:
Wait for the next version - Beta 04. I was working with the Miui earlier today and, to be honest, they have one messed up implementation. What appears to be happening is that the code is trying to run Darktremor twice...once directly via init.rc and another time via /system/bin/sysinit.

I ended up putting code in the program that should help this issue.

Also, it's the only rom that doesn't show any of my echo commands when I look at it from logcat, which makes it harder to diagnose.
[EVO 4G Android Development] tkirton:
I haven't seen it. In fact, I have a PM that I haven't answered yet asking me to do just that.

Samsung implements their roms differently than LG, Motorola, HTC and others. I've been trying to get this ported since the Samsung Moment was rooted.
[EVO 4G Android Development] tkirton:
Wait until Beta 04...there's issues when trying to upgrade the one on Miui. I've been working on the issue today trying to rework the program to make it run on Miui (amongst other Darktremor tasks).
[EVO 4G Android Development] freeza:
Okay cool, I'll wait. I'm running a modified fresh ROM though. Never tried MIUI.
[EVO 4G Android Development] tkirton:
I had issues with Burnt Droid at the start. It doesn't recognize any EXT partitions. It's the kernel they are using. Flash another kernel and it will probably work.

Here's the thing everyone has to remember...the kernel is the key to any ROM (and, unfortunately, to Darktremor). Let me give you an example:

For a while, I ran CyanogenMod nightly builds. The one compiled for the Evo actually had support for EXT3 and Darktremor would work perfectly on it. Then, I switched to a new kernel for CyanogenMod that would activate WiMAX...I wanted to test it. When I did that, Darktremor wouldn't mount anything anymore (program never changed and the rom didn't change also). The kernel didn't support EXT filesystems.

The point I'm making is this: If you are having a mounting issue on a rom, but wasn't having the same issue on another rom, it could very well be an issue with the kernel on that rom. The solution would be to flash a new kernel to your phone that does support EXT filesystems. Most kernels are very similar to each other as long as you stay with the kernels designed for your phone.

If you want to flash a new kernel and your phone doesn't have that nand protection on it, try the following:

1. Download a rom that has a kernel you know mounts your EXT partition.

2. Open that rom in your favorite file extraction utility and extract the boot.img file.

3. Push the boot.img file to your SD card (the FAT32 partition). I would use the following command: adb push boot.img /sdcard/

4. Once it is on your SD card, open up ADB shell (or a terminal emulator...just remember to type su first if you're going to do this in a terminal emulator)

5. Execute the command flash_image boot /sdcard/boot.img

6. Once that is done, reboot the phone and see if that resolves your issue.

I would love to have that much control over the kernel, but I simply don't...that's up to the rom developers.

As for the previous version, here's the FTP access to Darktremor's website with the directory that has all the versions of Darktremor created so far:

ftp://dtuser:Darktremor1@ftp.darktremor.info
[EVO 4G Android Development] tkirton:
Sorry...probably getting all my messages mixed up.

Wait...a modified FreshEvo? That didn't work?
[EVO 4G Android Development] freeza:
Well, I didn't bother to run an a2sd check once the ROM booted up. but I currently am using 2.7.5.2 with no problems. I flashed 2.7.5.3 beta 02, wiped cache/dalvik, and rebooted.

It was then that I realized the quick boot time meant no ext3 and from there the app drawer had none of my programs in it. So, I just assumed it was because of beta status and nandroided.

Should I give beta 03a a shot? :)
[EVO 4G Android Development] fixxxer2008:
well the excuses from the epic devs is they are waiting for official froyo to drop first! :rolleyes:

BUT if you can port it ill be glad to test for you and ill donate.
[EVO 4G Android Development] kminatta:
A2SD question

i am new to A2SD and i have searched everywhere for help. i have A2SD enabled (verified in terminal and shows 619 MB free of 959 MB under A2SD), but many of my installed applications show that they could be moved to SD when i go into "Manage Applications" under settings. should i move them to the SD card with "Manage Applications" or one of the APP2SD programs in the Market, or do i leave it alone? is there a way to make sure apps are moving to the SD via A2SD or a way to cause my apps to move again to the SD card? lastly, is there a website where i can get some very detailed instructions on using A2SD (i.e., what zipalign is, etc.)? Thanks!
[EVO 4G Android Development] dzuchowski:
I also would like to know also
[EVO 4G Android Development] dcharleyultra:
DT apps2sd uses the "a2sd" commands to work with applications. The initial invoking of DT moves all apps to the ext2/3/4 partition. "a2sd remove" moves the apps off the ex2/3/4 partition. "a2sd reinstall" moves them back.

I use Titanium Backup to check where my apps are stored: The initial page has storage data at the bottom. What you want is about at least 100MB of internal memory free, and your ext partition using a couple 100 or so MBs - depending on the number of apps you have installed.

I think the first couple of posts talk about or have links for the DT commands.

Note: the DT apps2d is different than the "native" Froyo apps2sd, and they use different parts of the sdcard.

Note 2: DT extends the "internal" memory space, so your apps may still have the "Move to SD Card" option, IIRC.
[EVO 4G Android Development] kminatta:
thanks for the help. so if the apps still have the "Move to SD Card" option, should i move them or not? is it just a case of the OS not recognizing that a2sd has moved them to the SD card already? also, i did a "a2sd reinstall" command after a2sd was already set up. it caused a few force closes and immediately rebooted my phone. could doing that if a2sd is set up correctly cause problems or break anything?
[EVO 4G Android Development] -Protos:
As it seems there is still a lot of confusion.

For newcomers, all that is needed is the 'a2sd reinstall' command, this will make ALL applications run from your SD Card.

If you want to run your Dalvik Cache from your SD Card that you should consider the 'a2sd cachesdreset' command (minimum class 4 recommended)
[EVO 4G Android Development] dzuchowski:
did the 2sd reinstall and rebooted

did the a2sd cachesdreset and rebooted and using a rom that has this cooked into it.... from your list of approved roms....
[EVO 4G Android Development] tkirton:
Try this: http://www.darktremor.info/files/a2sd/dtapps2sd-2.7.5.3-beta03b-signed.zip

This has a fix for a2sd and dtapp (used by the dtinstall script) that I am including in Beta 04. This should fix the issue of quick boot issue (which is Apps2SD thinking you are running it from the command line...Busybox PS kept saying that android.process.acore exists when it didn't....changed the PS command from Busybox to Toolbox.)
[EVO 4G Android Development] tkirton:
Well, then the excuse after Froyo will be they are waiting for Gingerbread to drop.

I'll see what I can do. I can't promise anything, but I'll try.
[EVO 4G Android Development] freeza:
Unfortunately, no go. Boot loops.

working ver: 2.7.5.2

dalvik-cache: cache partition

apps: 2GB EXT3

card: 32GB Class 10
[EVO 4G Android Development] FastJoe78:
Here's what you need to know...When you are in the app manager and you see apps on the SD tab they are actually on the FAT32 partition and not on the EXT2/3/4 partition. This is common with certain apps like google sky map and angry birds because they are coded to automatically install themselves on the FAT32 partition. When you see an app on the SD tab in app manager simply click on the move to phone(which is actually not the internal storage anymore but the EXT2/3/4 partition you created). By moving it from SD to phone from the native app manager you are tricking the OS into using DT a2sd which is different from froyo apps2sd...so if an app in the app manager says you can move it to phone go ahead and do that...This is rare and usually only happens for very large apps that were already designed to use the native apps2sd...I also recently became aware that after updates to certain apps they move themselves back to the FAT32 partition do to how they are written...simply go to app manager and move to phone anything showing on the SD tab and you are good to go....
[EVO 4G Android Development] ccossin:
I found a tool on Market called "Autostart (Root)" by blank-online.eu. Could this be used to utilize Darktremor on roms that don't have it cooked in?

If I understand it correctly it makes it possible to run scripts that the user creates on boot.

The description isn't exactly extensive.

This has been a telepathic transmission from the Outer Limits.
[EVO 4G Android Development] tkirton:
Try 04 Beta. And if that doesn't work...I don't know after that point. I do know I've fixed it on a couple of roms that were not moving past the boot screen.
[EVO 4G Android Development] tkirton:
Not in this particular case...the problem is that the EXT partition has to be mounted before the android.process.acore comes online, otherwise, you could go into a bootloop or have no applications (the latter could be fixed with the script...but Data2SD and Dalvik2SD will cause unpredictable operation).
[EVO 4G Android Development] ccossin:
Does that have something to do with /proc/filesystems? Mine mentions ext2 and ext3.

I looked around in my init.rc as well. I don't remember seeing anything that your dev guide said was necessary, but I am the rankest of amateurs with android/*nix.

This has been a telepathic transmission from the Outer Limits.
[EVO 4G Android Development] tkirton:
I can tell you the difference: 2.7.5.2 does a blind mount (it assumes your EXT is either on mmcblk0p2 or mmcblk1p2...you can't have it in any other position)

2.7.5.3 uses a combination of Busybox FDisk, Busybox Grep and Busybox Awk to mount your partition.

Since FDisk wasn't used in the previous version, I would suspect that is the issue.

What ROM are you using and I'll check it out. Maybe I can get a workaround for you.
[EVO 4G Android Development] freeza:
Fresh 3.5.0.1, but busybox version is like 1.18 or something. would that make any difference? I also have a bunch of crap stripped out of it.
[EVO 4G Android Development] tkirton:
That's strange...I tested 04 Beta on Fresh Evo 3.5.0.1 before I released it (that was earlier today) and it worked fine. In fact, I tested it with two different sets of code, the last code is the release code.

It shouldn't...but if you want to, run a2sd usedtbusybox and it will use the Busybox supplied with the Darktremor package (/system/bin/busybox.a2sd). See if that helps.

It may be you'll have to reflash Fresh Evo 3.5.0.1 on top of itself.
[EVO 4G Android Development] freeza:
I'll try that.

I'm trying to remember if I removed anything of significance. Would the SD card read_ahead fix going around have anything to do with it? I changed mine to 512KB...or perhaps recovery version? I am now using amon_ra's 2.3 test04...umm 32MB vm_heap size...sense apps almost entirely gone.
[EVO 4G Android Development] tkirton:
Could be. Darktremor has the SD card fix in it (which reminds me, I have to add that to changelog)...but I set mine to 128 as described by documents.

When I was experimenting with it, I set it to 256 and killed my battery (and I have one of those big Seidio 3500mAh battery). I had to wait for it to recharge in my Hero (as my Evo wouldn't recharge anything until I took the battery out for about 10 minutes...had a smaller battery I was trying to use until the big battery charged.)

Unless my experience was completely coincidence, my experience is that anything bigger than 128 and the phone becomes unpredictable. Not really sure why, though.
[EVO 4G Android Development] freeza:
:D Thanks, I may just revert back to 128 and remove the script since it is in netarchy's kernel already as well as DTA2SD. I'll let you know.
[EVO 4G Android Development] freeza:
Success! It was either the busybox version or the sd card tweak set to 512. I restored the busybox version that came with fresh and deleted the sd card tweak and beta 4 works!

Thanks for helping me troubleshoot.
[EVO 4G Android Development] jauger:
tkirton, Im trying this out with MikFroYo 4.5...on a clean install with beta4 it locks up on the splash screen...but I can re-flash dtapps2sd beta3 and it boots right up, Im digging through this thing trying to find whats causing the lock-ups, surely it cant be the sd-card tweak....
[EVO 4G Android Development] freeza:
Well dta2sd now includes the tweak as of beta 4 I think so possibly...maybe they're conflicting
[EVO 4G Android Development] EvoNotEvil:
miui and a2sd

okay so ive switched from sense running and older version od a2sd to miui and everything is great except upon original install but it seems if I try to switch kernels it breaks a2sd. Im currently running miui 1.28 which again works fine upon original install as did 1.22.2 but if I try to switch kernels(Ive tried many) including the kernel that came with 1.22 a2sd is no longer working. I came here and download the beta 04 and flashed and stuck at splash.. Hopefully this offers some insight to development. I would love to get this working. The kernel that comes with the latest official rel of Miui doest jive well with my batt..
[EVO 4G Android Development] CAL7:
DT installed correctly?

I have, I think successfully, installed apps2sd on my N1 (CM7 build 22). Titanium Backup shows the ext2 partition with 90MB used. And all my applications that used to be on the FAT32 partition have been moved to the phone, which I understand means that they are really on the ext2 partition of the sdcard.

But using terminal emulator to enter a2sd commands gives a bunch of errors (see below for "diskinfo"). Can someone tell me what the problem is? Much appreciated!

export PATH=/data/local/bin:$PATH
$ export PATH=/data/local/bin:$PATH
$a2sd diskinfo
rm: can't remove '/data/dta2sd.lg2': Permission denied
cp: can't create '/data/dta2sd.lg2': File exists
rm: can't remove '/data/dta2sd.lg1': Permission denied
cp: can't create '/data/dta2sd.lg1': File exists
rm: can't remove '/data/dta2sd.log': Permission denied
[ ] Apps2SD is launching...
/system/bin/a2sd: line 24: can't create /data/dta2sd.log: Permission denied
/system/bin/a2sd: line 25: can't create /data/dta2sd.log: Permission denied
/system/bin/a2sd: line 26: can't create /data/dta2sd.log: Permission denied
/system/bin/a2sd: line 35: can't create /data/dta2sd.log: Permission denied
/system/bin/a2sd: line 37: can't create /data/dta2sd.log: Permission denied
/system/bin/a2sd: line 38: can't create /data/dta2sd.log: Permission denied
/system/bin/a2sd: line 39: can't create /data/dta2sd.log: Permission denied
/system/bin/a2sd: line 40: can't create /data/dta2sd.log: Permission denied
/system/bin/a2sd: line 41: can't create /data/dta2sd.log: Permission denied
grep: /init.rc: Permission denied
tee: /data/dta2sd.log: Permission denied
__ _____
tee: /data/dta2sd.log: Permission denied
| \ |
tee: /data/dta2sd.log: Permission denied
| | |
tee: /data/dta2sd.log: Permission denied
|__/ | Darktremor Apps2SD 2.7.5.3 Beta 3a (2011-01-25)
tee: /data/dta2sd.log: Permission denied

/system/bin/launcha2sd: line 298: /data/dta2sd.log: Permission denied
[ ] GetProp Command = /system/bin/toolbox getprop
[ ] SetProp Command = /system/bin/toolbox setprop
[ ] Mount Point = /sd-ext
/system/bin/launcha2sd: line 467: /data/dta2sd.log: Permission denied
[ ] Starting Darktremor Apps2SD Version 2.7.5.3 Beta 3a
tee: /data/dta2sd.log: Permission denied
[ ] Launching Apps2SD Start Program with diskinfo
/system/bin/launcha2sd: line 881: /data/dta2sd.log: Permission denied
/system/bin/starta2sd: line 18: /data/dta2sd.log: Permission denied
[ ] Starting Darktremor Apps2SD in diskinfo mode
/system/bin/starta2sd: line 53: /data/dta2sd.log: Permission denied
tee: /data/dta2sd.log: Permission denied
[X] Invalid command: diskinfo
tee: /data/dta2sd.log: Permission denied
[ ] Setting File System Ready property to 1.
/system/bin/starta2sd: line 1428: /data/dta2sd.log: Permission denied
/system/bin/launcha2sd: line 883: /data/dta2sd.log: Permission denied
/system/bin/a2sd: line 43: can't create /data/dta2sd.log: Permission denied
$
[EVO 4G Android Development] tkirton:
Great...glad to hear that.

The Darktremor Beta 4 will still apply the tweak, but it will apply it at 128 per the original instructions.
[EVO 4G Android Development] tkirton:
I haven't tried it on 4.5, but my phone is currently running MikFroyo 4.4 and it is running perfectly with it.

Update: Just loaded both MikFroYo 4.5 Beta 5 and Darktremor Apps2SD 2.7.5.3 Beta 04 and it is working fine for me. Did an upgrade path rather than a full wipe.

Update2: Did a full wipe and monitored it. It rebooted twice like it suppose to, then it went to the MikFroyo splash screen for about two to three minutes. Now it's on the lock screen.
[EVO 4G Android Development] tkirton:
You have to run su first. Terminal emulators do not have immediate access to root, so you have to use the "su" command.

This is one of the reasons I always reference ADB, since you can skip this step in an ADB Shell.
[EVO 4G Android Development] CAL7:
Got it. Thank you very much.

(Sorry for cross posting here and at the Nexus One forum. This one was a mistake.)