yashsingh1/xdaforums huggingface dataset:
[Hero CDMA Android Development] KyleIsTheBeast:
Hands Free Actication?

I love this ROM, but I am having one problem. Every time I turn on my phone, right after the home page loads a black screen pops-up with a little gray bar in the middle and it is titled "Hands Free Activation" and it says loading underneath. I let it run, but then it fails and said "Contact your service provider bla bla bla" lol well, anyone know how to get this to stop? Or what this is? I can press "Cancel" every time, but it is just a little aggravating. Thanks! :D
[Hero CDMA Android Development] superlinkx:
You might want to make sure your PRI isn't messed up. Sounds like an issue with your service provider not recognizing your phone. I noticed you aren't using Sprint, so using this ROM may not work for you. I'm only guessing, so hopefully this helps. Anyone else can correct me if I'm wrong.
[Hero CDMA Android Development] tkirton:
Eclair is bigger in size overall than Cupcake, so it will use up more space. How much more, I'm not sure, since I'm not certain the leaks are optimized.

But...I have been working on a newer version of a2sd/apps2sd which does a few new things:

1. Allows the user to setup all the components of a2sd/apps2sd via command prompt (a2sd install or apps2sd install)

2. Allows for moving of the dalvik-cache to sd card for those who already have apps2sd or a2sd setup (a2sd cache or apps2sd cache). The process can be reversed (a2sd nocache or apps2sd nocache)

3. Allows for the user to specify if the swap partition will be turned on or off (a2sd swap or apps2sd swap)..(a2sd noswap or apps2sd noswap)

4. Creates flag files on /system/sd to indicate when a2sd/apps2sd is not to be loaded (for those who want to keep an ext partition, but don't want to use it just yet), when swap is to be activated and if dalvik cache is to be automatically moved. This is great when you testing ROMs.

5. Help screen (a2sd help or apps2sd help)

6. Allows the user to reverse the a2sd/apps2sd installation (a2sd remove or apps2sd remove).

I've tested this as much as I can, but I need beta testers to help out.

The files are located at http://www.darktremor.com/upload/a2sd-2.5.zip

Once you get the files, uncompress it. It should create a system directory, with three directories (bin, xbin and lib) and several files (3 in bin, 3 in xbin and 6 in lib)

The, at a shell prompt, type the following commands in the system directory (the one you extracted):

adb remount

adb push . /system

This should place the entire structure and files on the phone.

If you are running Windows, you may have to execute the following:

adb shell "chmod 777 /system/etc/init.d/04apps2sd"

adb shell "chmod 777 /system/bin/a2sd"

adb shell "chmod 777 /system/bin/apps2sd"

adb shell "chmod 777 /system/bin/e2fsck"

adb shell "chmod 777 /system/xbin/a2sd"

adb shell "chmod 777 /system/xbin/apps2sd"

adb shell "chmod 777 /system/xbin/e2fsck"

I'll work on an installer next (or better yet, how to sign a zip).

You can then reboot or execute a2sd help (or apps2sd help) to get a list of commands.

Note: The dalvik-cache will not automatically move when the phone is rebooted. Dalvik starts either before or at the same time a2sd/apps2sd start, which means it is reading/compiling at the same time a2sd/apps2sd is attempting to move the dalvik-cache. The causes the phone to go into an infinite loop. To move the cache, shell into the phone (adb shell) and run a2sd cache or apps2sd cache from the /system/bin or /system/xbin directory. You can move the cache once the phone is booted, but not while it is booting. If you reboot the phone without moving the dalvik-cache, it will set up the folders as if you cleared your cache. That will force Dalvik to recreate the contents of the cache, increasing boot time during that boot cycle. Next reboot will not have to recreate the cache.

Dalvik cache is taking up a lot of space. Mine went from 84MB to 109MB just by moving the cache to the SD card.

If anyone has issues with it, let me know (you can pm me).
[Hero CDMA Android Development] smw6180:
Couple of things right off the bat:

chmod 0755 /system/bin/a2sd

chmod 0755 /system/bin/apps2sd

chmod 0755 /system/bin/e2fsck

chmod 0755 /system/xbin/a2sd

chmod 0755 /system/xbin/apps2sd

chmod 0755 /system/xbin/e2fsck

About to boot up and move my dalvik-cache. Will let you know what happens at reboot (I'll edit this post).

Edit: lol...you were evidently editing yours as I was entering mine. ;)

Edit: Seems to be working. If I understand you correctly though (tell me if I missed something) this is going to rebuild Dalvik every time I boot, if I don't do an a2sd nocache, correct? This seems to indicate that in order to make this work, I'll have to do an adb shell / a2sd cache every time I reboot the phone.

I'm sitting at 116/160mb free right now. Pretty sweet. :)

Another Edit:

Yep, that's exactly what happens. The dalvik-cache recreates itself at boot time. Bummer. That seems to indicate that we have to do this each time after it boots.
[Hero CDMA Android Development] tkirton:
It works fine without the chmod if you are in linux...but I forgot about Windows when I wrote that and had to go back and edit.
[Hero CDMA Android Development] smw6180:
Yep. Windows strips the executable bit when you copy it over.
[Hero CDMA Android Development] MikeMcG:
Does anyone have a zip of the Matrix bootscreen?
[Hero CDMA Android Development] adamboyd83:
This being the first 2.1 ROM I have tried I like it a lot. Battery is good enough for me to use it till the official release. Only thing that I have noticed that is weird is the phone sometimes doesn't sleep when the phone is charging. At least that's what was happening yesterday but it seemed to have today. Also I flashed the clear lock screen and it got rid of the color slider bar icons.
[Hero CDMA Android Development] tkirton:
Here's how it works:

If you just boot the phone without doing a2sd cache or a2sd nocache, the program will look to see if the symbolic link for dalvik-cache is present. If it is, it skips the move process.

If the /data/dalvik-cache is a directory rather than a symbolic link, it will do the following:

1. Look for /system/sd/.nocache and, if present, skip the move process (more on that file later)

2. Create /system/sd/dalvik-cache (if it doesn't exists) or clear out /system/sd/dalvik-cache of any files (if it does exists)

3. Remove /data/dalvik-cache

4. Create the symbolic link for /data/dalvik-cache to /system/sd/dalvik-cache.

Since the files cannot be moved while the phone is booting, the files are simply eliminated. This causes Dalvik to restart (just Dalvik, not the phone itself). When that happens, Dalvik sees there is no cache files and rebuilds them.

Next time you boot, a2sd will skip the Dalvik-cache move since the /data/dalvik-cache is a symbolic link.

If you execute a2sd cache when the phone is completely booted, it will do the following:

1. Create or Clear /system/sd/dalvik-cache

2. Move all files from /data/dalvik-cache to /system/sd/dalvik-cache

3. Remove /data/dalvik-cache

4. Creates the /data/dalvik-cache symbolic link to /system/sd/dalvik-cache

5. Remove the file /system/sd/.nocache (more on this file later)

Upon reboot, the Dalvik-cache will not be moved as the symbolic link is already present.

If you execute a2sd nocache, the following happens:

1. Removes the symbolic link /data/dalvik-cache

2. Creates the directory /data/dalvik-cache

3. Moves the files from /system/sd/dalvik-cache to /data/dalvik-cache

4. Creates /system/sd/.nocache

/system/sd/.nocache is a file that is used to tell a2sd that you don't want the dalvik-cache moved from the internal memory. If that file isn't present, a2sd will perform the dalvik-cache move (the one that doesn't copy files).
[Hero CDMA Android Development] smw6180:
Problem I'm having is that it's evidently not caring about the symlink. It's removing it, then recreating dalvik-cache, each reboot (after a2sd cache, that is). Let me try it once more and see what I see. I had this also happen when doing it manually, so it's possible the problem is on my end....although I'm not sure why it would remove the symlink and recreate it, but...
[Hero CDMA Android Development] tkirton:
I wonder if that's something in Fresh 2.0d. I'm using DamageControl 2.05 and don't have that issue.

I'll flash Fresh 2.0d and see if I can duplicate the issue.
[Hero CDMA Android Development] smw6180:
Could be. I switched from 2.05 to test Flipz' version a couple of days back. I'm making notes and I'll post 'em when it's done booting. But it looks to me like Dalvik is ignoring the symlink, or treating it like it's not there, then re-creating the dalvik-cache under /data

Here's what I see when I do it:

# a2sd cache

a2sd cache

[*] Starting A2SD version 2.5 beta 1

[ ] Starting Dalvik-cache move to SD card.

[ ] Removing contents of /system/sd/dalvik-cache

[ ] Copying /data/dalvik-cache to /system/sd/dalvik-cache

[ ] Removing /data/dalvik-cache

[ ] Linking /data/dalvik-cache to /system/sd/dalvik-cache

[ ] Setting ownership...

[ ] Setting permissions...

[*] Move complete.

ls -l /data

lrwxrwxrwx root root 2010-04-04 08:24 dalvik-cache -> /system/sd/dalvik-cache

ls -l /system/sd

drwxrwx--x system system 2010-04-03 22:57 app

drwxrwx--x system system 2010-04-03 22:57 app-private

drwxrwxrwx root root 2010-04-04 08:24 dalvik-cache

After reboot:

ls -l /data

drwxrwx--x system system 2010-04-04 08:26 dalvik-cache

ls -l /system/sd

drwxrwx--x system system 2010-04-03 22:57 app

drwxrwx--x system system 2010-04-03 22:57 app-private

drwxrwxrwx root root 2010-04-04 08:24 dalvik-cache

As you can see, the symlink is gone, and dalvik-cache has been recreated. And my phone is currently stuck at the long HTC screen while it rebuilds.
[Hero CDMA Android Development] tkirton:
That is definitely odd. That has to be something with Fresh 2.0d. I'm flashing my phone right now and I'll see if I can reproduce it.

EDIT: Definitely Fresh 2.0d...now mine's doing it. He must be recreating it in init.rc. I think I can compensate.
[Hero CDMA Android Development] smw6180:
Good deal. If you can't, I'll nuke and pave and try it again. As I said it COULD be my install. I'd be surprised, but it's not outside the realm of possibility.
[Hero CDMA Android Development] tkirton:
Nope...now mine is doing it with Fresh 2.0d. Flipz is doing something different (or the base he's using is doing something different). I may be able to compensate.
[Hero CDMA Android Development] smw6180:
Well at least it's consistent. I'll be around if you want to test.

For what it's worth I nandroided back to DC 2.05 and it works perfectly. Just restored flipz' rom and I'm ready to test for you. :)
[Hero CDMA Android Development] :
One mirror thing I noticed is that in the build.prop

ro.build.version.release=2.1-update2 (freshhh)

causes the quick search bar not to offer web suggestions.

The exception browser kept saying illegal character. Not sure if it is the space between update2 and (freshhh) or the '(' itself

My remedy was to remove the (freshhh) 'sorry' from build.prop push it back and reboot.
[Hero CDMA Android Development] ASULutzy:
I just woke back up, but I see your script. I did the script commands manually before you posted that script and experienced the same problem. The dalvik-cache is recreated in internal memory on reboot even if the symlink is present.

I'll try and dig through some stuff and see why in the heck that is happening.
[Hero CDMA Android Development] tkirton:
Found it...the apps2sd is in an entirely different location: /system/etc/init.d

And, in that file, it's erasing the dalvik-cache each time.

I'll fix it once and for all.
[Hero CDMA Android Development] smw6180:
Woot! Show it who's boss! :)
[Hero CDMA Android Development] :
I copied the apps2sd from Fresh 2.0b over the one in /system/etc/init.d
[Hero CDMA Android Development] ASULutzy:
Ah you found it. Yea, in /system/etc/init.d/04apps2sd

It's checking for symlinks in /data/ and then erasing them and recreating the directories, then when it gets to the part that is supposed to reset them up, it neglects to do so for dalvik-cache even though the comment says it's going to o.O

Also, I noticed that in /etc/init.rc it will attempt to create the cache and change the owner and permissions on it, but I think that should be okay because the mkdir should fail if there's already a symlink and the permission changes will be applied to the symlink (which should be fine since those are presumably the correct permissions)
[Hero CDMA Android Development] dcdave63:
Will this be a fix that can be flashed via recovery once and only once as a signed zip? Or something that flipz needs to include in his next version?
[Hero CDMA Android Development] ASULutzy:
I don't want to speak for the guy that is actually taking the lead and doing the work, but presumably you could just push a script without bugs and it would work. Don't know much about how to actually sign stuff or I'd try and make a flashable patch.
[Hero CDMA Android Development] smoother2010:
glad to see there is a fix coming, i was just about to reflash this morning too, ;)
[Hero CDMA Android Development] tkirton:
Okay...download http://www.darktremor.com/upload/a2sd-2.5.zip again.

Add this command to the command you have to do a chmod on:

adb shell "chmod 777 /system/etc/init.d/04apps2sd"

Run the a2sd cache command again, then reboot.

This time, it should work. It held on my setup.
[Hero CDMA Android Development] ItsDon:
Any idea when/if a fix may be coming for a working MNS on PRI 1.70_003?
[Hero CDMA Android Development] smoother2010:
what steps do we take to install this? sorry if i missed something?
[Hero CDMA Android Development] smw6180:
grabbing it now, will report back.
[Hero CDMA Android Development] tkirton:
All the ROMs, including 1.5, have a mkdir command in init.rc that will create the dalvik-cache. This command will simply fail if the directory, file or symlink is present.

The apps2sd in init.d is deleting the symlink for /data/data, which was in the original Cyanogen script, but the deletion of dalvik-cache is something completely new. I went back to the original script and it's not there.

Not sure what the reasoning for recreating the dalvik-cache, other than if the SD is pulled or the directory doesn't exists, the phone will hang (which was happening to me when the entire script wouldn't load).

I could put some provisions in there that state if the /data/davlik-cache is linked and the /system/sd/davlik-cache isn't present, either create /system/sd/davlik-cache or, if there's no ext2/3 partition, recreate the folder.

But that's for a later time.
[Hero CDMA Android Development] smoother2010:
sorry if im a noob but how do we install this? is this a flashable zip? :confused:
[Hero CDMA Android Development] smw6180:
Unfortunately it didn't seem to work.

a2sd cache

[*] Starting A2SD version 2.5 beta 1

[ ] Starting Dalvik-cache move to SD card.

[ ] Removing contents of /system/sd/dalvik-cache

[ ] Copying /data/dalvik-cache to /system/sd/dalvik-cache

[ ] Removing /data/dalvik-cache

[ ] Linking /data/dalvik-cache to /system/sd/dalvik-cache

[ ] Setting ownership...

[ ] Setting permissions...

[*] Move complete.

# ls -l /system/sd

ls -l /system/sd

drwxrwx--x system system 2010-04-03 22:57 app

drwxrwx--x system system 2010-04-03 22:57 app-private

drwxrwxrwx root root 2010-04-04 10:14 dalvik-cache

ls -l /data

lrwxrwxrwx root root 2010-04-04 10:14 dalvik-cache -> /system/sd/dalvik-cache

After reboot:

ls -l /system/sd

drwxrwx--x system system 2010-04-03 22:57 app

drwxrwx--x system system 2010-04-03 22:57 app-private

drwxrwxrwx root root 2010-04-04 10:14 dalvik-cache

ls -l /data

drwxrwx--x system system 2010-04-04 10:16 dalvik-cache

and my dalvik-cache is in the process of rebuilding.
[Hero CDMA Android Development] tkirton:
Flipz is more than welcome to take the code and do what he wants with it.

As for a signed zip...I'm working on doing that, but if anyone wants to sign it, they can take the zip the way it is and do it. I have no issue with that.
[Hero CDMA Android Development] smoother2010:
thanks for your work, ill wait for a signed zip to flash. :p
[Hero CDMA Android Development] tkirton:
Look at /system/etc/init.d/04apps2sd and tell me the size on that file?

Maybe it didn't transfer correctly here.
[Hero CDMA Android Development] smw6180:
ls -l /system/etc/init.d/04apps*

-rwxrwxrwx root shell 2885 2008-08-01 08:00 04apps2sd

I just noticed that file doesn't seem to be in the zip.
[Hero CDMA Android Development] smoother2010:
different topic but can we delete rosie using flips kitchen with no error occurring on the phone? i much prefer to not run sense or have it installed.
[Hero CDMA Android Development] tkirton:
Here's the link (it's rather lengthy): http://xdaforums.com/showpost.php?p=6083048&postcount=2238
[Hero CDMA Android Development] tkirton:
How big is your a2sd in your /system/bin?
[Hero CDMA Android Development] tkirton:
Okay...I check it again.

EDIT: It's on Darktremor. I've renamed it: http://www.darktremor.com/upload/a2sd-2.5b.zip

You should have four directories under system: /bin /xbin /lib and /etc. Under /etc, there should be an init.d folder. Under that is the file 04apps2sd.

Worse Case Scenario: If the a2sd in /system/bin is current, then you can execute the following commands:

rm /system/etc/init.d/04apps2sd

ln -s /system/bin/a2sd /system/etc/init.d/04apps2sd
[Hero CDMA Android Development] smoother2010:
WOW...im no good at command lines, ill wait for a flashable zip, thanks.
[Hero CDMA Android Development] smw6180:
cd /system/bin

# ls -l a2sd

ls -l a2sd

-rwxrwxrwx root root 15142 2010-04-04 10:11 a2sd
[Hero CDMA Android Development] smoother2010:
heres a question for you, when the final sprint 2.1 comes out and the devs here make custom roms with apps2sd will we still have these issues? i mean could the problem be these builds are still not finished yet or beta's?
[Hero CDMA Android Development] smw6180:
Yes, we're likely to have a few configuration issues here and there. It's all part of the process of taking stock and making it work PROPERLY. ;)
[Hero CDMA Android Development] david279:
We could find out how to use the new way of app2sd cyanogen been using. Where you can select where you want to install your app on each install.(either ext or internel)
[Hero CDMA Android Development] tkirton:
I have 15141 (corrected an error that prevents the phone from booting when it is 04apps2sd.

You may want to download again. New filename is a2sd-2.5b.zip
[Hero CDMA Android Development] smw6180:
Working on it. And yes this zip has the etc directory in it. Going to do it from scratch as a valid test and let you know. I'll report back in a few minutes.
[Hero CDMA Android Development] tkirton:
That would be good. Since I'm somewhat there with this 2.5 build, I don't think it would take much to modify either scripts for us.

I just need to get a hold of the script itself.
[Hero CDMA Android Development] tkirton:
Okay...if I can't figure out how to do one, I may get one of the developers to build me one.
[Hero CDMA Android Development] smw6180:
a2sd cache

[*] Starting A2SD version 2.5 beta 1

[ ] Starting Dalvik-cache move to SD card.

[ ] Removing contents of /system/sd/dalvik-cache

[ ] Copying /data/dalvik-cache to /system/sd/dalvik-cache

[ ] Removing /data/dalvik-cache

[ ] Linking /data/dalvik-cache to /system/sd/dalvik-cache

[ ] Setting ownership...

[ ] Setting permissions...

[*] Move complete.

# ls -l /data

ls -l /data

lrwxrwxrwx root root 2010-04-04 10:36 dalvik-cache -> /system/sd/dalvik-cache

ls -l /system/sd

drwxrwx--x system system 2010-04-03 22:57 app

drwxrwx--x system system 2010-04-03 22:57 app-private

drwxrwxrwx root root 2010-04-04 10:36 dalvik-cache

ls -l /system/etc/init.d/04apps2sd

-rwxrwxrwx root root 15141 2010-04-04 10:34 04apps2sd

After reboot:

ls -l /data

lrwxrwxrwx root root 2010-04-04 10:36 dalvik-cache -> /system/sd/dalvik-cache

Looks like we have a winner.

busybox df -h

Filesystem Size Used Available Use% Mounted on

tmpfs 95.5M 0 95.5M 0% /dev

tmpfs 4.0M 4.0K 4.0M 0% /sqlite_stmt_journals

/dev/block/mtdblock3 170.0M 136.6M 33.4M 80% /system

/dev/block/mtdblock5 159.5M 16.3M 143.2M 10% /data

/dev/block/mtdblock4 130.0M 1.1M 128.9M 1% /cache

/dev/block/mmcblk0p2 457.4M 87.9M 345.1M 20% /system/sd

/dev/block//vold/179:1

7.1G 926.6M 6.2G 13% /sdcard

Now the question is: Is this compatible with Damage Control, or do we need to use the zip you posted there for that one?
[Hero CDMA Android Development] tkirton:
It should be compatible, as DC2.5 does a direct call to /system/bin/a2sd from init.rc. However, give me a few minutes and I will test that.
[Hero CDMA Android Development] ASULutzy:
For those scared it really isn't hard to do. I just did ./adb push /path/to/unzipped/system /system

./adb shell

a2sd cache

If you are running windows you might have to chmod all the scripts

chmod 0755 /system/bin/a2sd

chmod 0755 /system/bin/apps2sd

chmod 0755 /system/bin/e2fsck

chmod 0755 /system/etc/init.d/04apps2sd

chmod 0755 /system/xbin/a2sd

chmod 0755 /system/xbin/apps2sd

chmod 0755 /system/xbin/e2fsck

edit: totally worked and held after reboot, went from like 74 MB free to 129!
[Hero CDMA Android Development] smw6180:
Sounds good. If it works between roms it will be extremely convenient to switch back and forth.

Great work, thank you for putting in the time on this.

Oh and after some testing (class 6 8gb SD card) no issues whatsoever with speed. If anything (probably placebo effect) program load times seem faster to me.
[Hero CDMA Android Development] tkirton:
add the following:

chmod 0755 /system/etc/init.d/04apps2sd

In Fresh 2.0d, the 04apps2sd is the script itself.
[Hero CDMA Android Development] sdotcarlisle:
but i'm so sared lol. is the "./ " just after you do the cd c:/android-sdk/tools prompt then finish with the script? where would we put the file name?
[Hero CDMA Android Development] smw6180:
Here's a batch file I wrote to handle doing the permissions. Shove the attachment in the same directory as adb (\install_path\android-sdk-windows), type 'rename perms.doc perms.bat' and run it.
[Hero CDMA Android Development] smoother2010:
i hope flips will incorp this fix into another rom, for now ive decided to go back to pancake 1.5 where everything work out of the box. :) thanks to the devs for all of the hard work and happy easter!
[Hero CDMA Android Development] tkirton:
And the answer is, yes.

DamageControl doesn't have an init.d directory. The push will put one there, but the init.rc isn't setup to use it. It will use /system/bin/a2sd.
[Hero CDMA Android Development] smw6180:
Excellent. Great work, thanks again! :)
[Hero CDMA Android Development] tkirton:
No problem. If you have any issues, let me know.
[Hero CDMA Android Development] ASULutzy:
So what of the pros and cons of actually having the dalvik cache on the sdcard? I see that /data/data being moved to the sdcard would cause stability issues, is there any compelling reason to leave the dalvik-cache in internal memory? I notice that my internal storage stays constant now at 129 MB no matter what I do or what programs I open?

Unused memory = useless memory, so now I'm torn :rolleyes:
[Hero CDMA Android Development] PRGUY85:
Have been using this ROM for 2 days, and its stellar. I came from DamageROM which was awesome, but this gives me much better battery life. My phone is at 40% and was unplugged 28 hours ago. Only problem for me is that I'm not getting my contacts to sync to their Facebook pictures.
[Hero CDMA Android Development] smoother2010:
wow.. going back to pancake 1.5 and i installed more apps than i did on this rom and i still have 105mb free compared to 79mb with flips rom. it's like night & day with the speed too. no offense but i think running a rom without sense installed is much faster and stable. :eek:
[Hero CDMA Android Development] AH28:
The fix did not help me, I still cannot hear callers and they cannot hear me... any ideas? The ROM is great otherwise...