yashsingh1/xdaforums huggingface dataset:
[Desire Android Development] tkirton:
You wouldn't. I noticed that the Cyanogen builds are using the following line in init.rc:

exec /system/bin/sysinit

And /system/bin/sysinit has the following line:

/system/bin/logwrapper /system/xbin/busybox run-parts /system/etc/init.d

...which is the run-parts method in my guide.

If exec actually stops the init.rc and runs the program, then there is no reason to modify the init.rc...the exec would accomplish the same thing as these lines:

start sysinit

if property:cm.filesystem.ready=1

class_start default

service sysinit /system/bin/logwrapper /system/xbin/busybox run-parts /system/etc/init.d

disabled

oneshot

I'm looking into the behavior of the exec command and see if that is, in fact, what it is doing. But if it is working for you, then you don't have to modify the init.rc.
[Desire Android Development] andycted:
I've removed everything that deleted and copied DATA partition I think. I also only tried to remove all the delete recursive and once I think I've only removed the delete DATA thing.

Sorry, can't remember more precisely, anyway the result was mixed but never final.

by the way, I wiped and applied the new nightly, then applied your RC2, without the patch that was noted in cyanogen thread. No problems until now.
[Desire Android Development] andycted:
I found my last modification, which kind of worked until I tried to flash something else from recovery:

assert compatible_with("0.2") == "true"

show_progress 0.1 0

delete_recursive SYSTEM:etc/init.d

delete SYSTEM:bin/launch.a2sd

delete SYSTEM:bin/setup.a2sd

delete SYSTEM:bin/boot.a2sd

delete SYSTEM:bin/align.a2sd

delete SYSTEM:bin/repair.a2sd

delete SYSTEM:bin/start.a2sd

delete SYSTEM:bin/jit.a2sd

delete SYSTEM:bin/reboot.a2sd

delete SYSTEM:bin/setupa2sd

delete SYSTEM:bin/aligna2sd

delete SYSTEM:bin/a2sd

delete SYSTEM:bin/apps2sd

delete SYSTEM:xbin/a2sd

delete SYSTEM:xbin/apps2sd

delete SYSTEM:bin/launcha2sd

delete SYSTEM:bin/boota2sd

delete SYSTEM:bin/starta2sd

delete SYSTEM:bin/chka2sd

delete SYSTEM:bin/fixa2sd

delete SYSTEM:bin/jita2sd

delete SYSTEM:bin/e2fsck

delete SYSTEM:xbin/e2fsck

show_progress 0.1 0

copy_dir PACKAGE:system SYSTEM:

show_progress 0.1 0

set_perm 0 0 0777 SYSTEM:bin/a2sd

set_perm 0 0 0777 SYSTEM:bin/fixa2sd

set_perm 0 0 0777 SYSTEM:bin/boota2sd

set_perm 0 0 0777 SYSTEM:bin/chka2sd

set_perm 0 0 0777 SYSTEM:bin/starta2sd

set_perm 0 0 0777 SYSTEM:bin/bash

set_perm 0 0 0777 SYSTEM:bin/e2fsck

set_perm 0 0 0777 SYSTEM:bin/busybox.a2sd

set_perm 0 0 0777 SYSTEM:bin/apps2sd

set_perm 0 0 0777 SYSTEM:xbin/a2sd

set_perm 0 0 0777 SYSTEM:xbin/apps2sd

set_perm 0 0 0777 SYSTEM:etc/init.d/04apps2sd

set_perm 0 0 0777 SYSTEM:etc/init.d/00banner

set_perm 0 0 0777 SYSTEM:etc/init.d/01sysctl

set_perm 0 0 0777 SYSTEM:etc/init.d/02firstboot

set_perm 0 0 0777 SYSTEM:etc/init.d/03modules

set_perm 0 0 0777 SYSTEM:etc/init.d/99complete

set_perm 0 0 0777 SYSTEM:xbin/e2fsck

set_perm 0 0 0777 SYSTEM:bin/zipalign

set_perm 0 0 0777 SYSTEM:bin/launcha2sd

set_perm 0 0 0777 SYSTEM:bin/jita2sd

set_perm 0 0 0644 SYSTEM:bin/apps2sd.hlp

set_perm 0 0 0777 SYSTEM:sd

show_progress 0.1 10
[Desire Android Development] tkirton:
So, maybe the exec does the exact same thing as the patches that I have. If so, that is a lot simpler than the two patches.
[Desire Android Development] tkirton:
Hmmmm....

1. Do you see a mmcblk0p2 in /dev/block?

2. Do you see a directory called sd in /system

I got a feeling the /system/sd mount is disappearing when you update CyanogenMod.

I'm testing a new version of 2.7.5 (Release Candidate 3). In that version, I'm moving the mount from /system/sd to /data/sd (this will avoid the NAND protection crap that keeps messing with the program). You're more than welcome to test it to see if it resolves your issue:

http://www.darktremor.info/files/a2sd/dtapps2sd-2.7.5-rc3-signed.zip

Right now, I'm having some force close issues on some of the programs (not sure if that was because of this copy or because I messed up the program earlier this morning...that issue is fixed in the one that is on the web server). Reinstalling the programs in question seems to fix the issue, so I'm thinking it was just because I messed something up earlier this morning in testing.
[Desire Android Development] andycted:
I'm more than eager to test what you said, but right now my girlfriend is exercising her right to have me 20 minutes a day away from this phone.

Will report later, thanks
[Desire Android Development] tkirton:
No problem.
[Desire Android Development] andycted:
This is with RC2:

C:\Program Files\android\android-sdk_r05-windows\android-sdk-windows\tools>adb shell ls /dev/block

loop0 loop3 loop6 mmcblk0p1 mtdblock1 mtdblock4

loop1 loop4 loop7 mmcblk0p2 mtdblock2 mtdblock5

loop2 loop5 mmcblk0 mtdblock0 mtdblock3 vold

C:\Program Files\android\android-sdk_r05-windows\android-sdk-windows\tools>adb shell ls /system

app build.prop fonts lib media usr

bin etc framework lost+found sd xbin

while it's booting with usb connected. It ends as expected as before with bootloop and the directories are there. I'm going to try with RC3 and report.

Also I might just add that in the cyanogen thread many people report updating without problems. Don't know if it's because I have 100+ applications installed
[Desire Android Development] tkirton:
I reworked some of the code since we last talked, so it may work better. I just put the updated copy of RC3 on the web server.
[Desire Android Development] andycted:
Previous link to RC3 gives me page not found

EDIT: works now
[Desire Android Development] andycted:
restored, updated and applied RC3, directories are still there same as before... booting now ...

I'm seeing the same failed messages because of insufficient space...bootloop !

Could it be a problem with the dalvik cache that isn't on the sd card yet ? Is there a way to apply the "a2sd cachesd" command before booting ?
[Desire Android Development] nespresso33:
What is the difference between your apps2sd and apps2sd from other rom
[Desire Android Development] tkirton:
If you downloaded RC3 earlier, clear your browser cache first, then download it again. I have seen browser cache just give you the same file even though it looks like it is downloading a new one.

Dalvik-cache is set for internal storage (/data/dalvik-cache). It runs without dalvik-cache being moved.

What could be happening is that the dalvik-cache may be on the /cache partition and the dalvik-cache directory was removed.

Easiest way to find out:

In an ADB Shell, type ls -la /data

Look for an entry called dalvik-cache. Look to the far right of the entry. If you don't see something that starts with "->", then the dalvik-cache is running on internal storage. However, if you do see a "->", look further to the right to see where it is pointing.

Now, if it says "/system/sd/dalvik-cache" or (in RC3) "/data/sd/dalvik-cache", then type the following command:

ls -la /system/sd (or ls -la /data/sd if running RC3)

Look for the entry dalvik-cache. If you don't see one, the directory was knocked out. Simply create a new directory using the following commands:

For RC2 and earlier:

busybox mkdir /system/sd/dalvik-cache

busybox chmod 777 /system/sd/dalvik-cache

For RC3 and later:

busybox mkdir /data/sd/dalvik-cache

busybox chmod 777 /data/sd/dalvik-cache

Now, if the entry points to /cache/dalvik-cache, type ls -l /cache and see if you see a dalvik-cache entry. If you don't, type the following:

busybox mkdir /cache/dalvik-cache

busybox chmod 777 /cache/dalvik-cache

That should resolve your issue. I would reboot right after that and see if that helps. Remember, if you had to create those directories, then DalvikVM has to rebuild the dalvik-cache...this could take about five minutes.

After reboot, perform the checks stated above again to make sure dalvik-cache did not move.
[Desire Android Development] tkirton:
I probably was updating...I'm updating using a data card from Sprint (EVDO Rev. A...not slow, but certainly nothing like my home internet).
[Desire Android Development] tkirton:
Usually, you just run it while the phone is booted.

And the getprop notifications may be due to you being in recovery. Try this command when your phone is booted: a2sd check.

That command checks your setup, but doesn't do anything more than that. If you are still getting getprop messages with that command, then you have something not set right in your rom.
[Desire Android Development] tkirton:
I tend to put more features in mine and mine isn't specific to any particular rom or phone.
[Desire Android Development] andycted:
Thanks a lot for your help. The problem was that I had to run that command in recovery because after updating and applying your script, I ended in a bootloop. I don't know if you saw my late edit, but after running the command (a2sd cachesd) in recovery, even with all those errors, the phone booted ok and I'm running it without problems since then. I also deleted my dalvik cache manually.

I've also checked the symlink and physical directory for the dalvik cache right now and they are both there, but I should have probably checked them when I had bootloops, didn't occur to me. Next time I'll update I'll try, maybe the others who updated correctly CM6 nightlies didn't have it moved to the sd to begin with. I guess this could also explain why it worked after I run 'a2sd cachesd' ???

EDIT: I'm trying to update to 14/08 build and see with adb if the symlink is there when/if I end up in a bootloop.
[Desire Android Development] andycted:
Ok I've finished updating and it's booting up. I expect it to be a bootloop because apparently /data/dalvik-cache is not symlinked and resides on internal storage. I can repeat the a2sd cachesd command from recovery, but is there a better way to avoid those errors ?

EDIT: tried with

rm -r /data/dalvik-cache

ln -s /data/sd/dalvik-cache /data/dalvik-cache

(/data/sd/dalvik-cache is already there)

booting right now, let's see...

LAST EDIT: it worked ! So I think the only problem is the symlink getting lost after the update
[Desire Android Development] andycted:
Do you think flashing an update script like this

delete_recursive DATA:dalvik-cache

symlink /data/sd/dalvik-cache /data/dalvik-cache

After yours would be enough to solve the problem with the symlink getting lost ? I tried something like that yesterday, but I actually had to run it again, AFTER it had booted at least once.

I will try it tonight, anyway.
[Desire Android Development] kay9jay:
Data/data folders to system/sd ? ? ? ? ? ? ?

@ tkirton

is there a way to move SOME subfolders from data/data/ to sd ext3 ?

i am asking because some apps like iGo navigation, google earth and gameloft games put A LOT of data in data/data/

e.g. google eart and iGo -> ~18mb each.

i have cache, app and app-private on sdcard already but ran out of space on phone memory anyways because of data/data/

i tried moving folders to sd and sysmlinking them.

i am not sure if this works. afaik one shouldnt move the data/data/ folder itself because some subfolders NEED to be in phone memory for stability reasons.
[Desire Android Development] tkirton:
I resolved the issue with RC3. There will be two packages that I will maintain. One is for new installations and one is for updating. The update version will not alter the dalvik-cache setting.

http://www.darktremor.info/files/a2sd/dtapps2sd-2.7.5-rc3-update-signed.zip
[Desire Android Development] tkirton:
I got to admit, that is rather large lettering, almost like shouting.

To answer your question, make a data directory on the SD card.

Then create the application's directory (as it looks in /data/data) on the SD card.

Next, copy the entire contents of the application directory to the data directory on the SD card

Then you delete the directory in /data/data and create a symlink.

That, in theory, should work (personally, I never tried it).
[Desire Android Development] gapone:
I'm stuck at htc (phone is htc desire with latest cm6 nightly 180810) boot logo. This is after I install RC3 (tried both versions). If I install RC2, no problems. So there is something wrong with the rc3...
[Desire Android Development] tkirton:
The difference between RC2 and RC3 is where the mount is...in RC2, it's /system/sd. In RC3, it's /data/sd.

If you can get into your phone using ADB shell:

Send me the dta2sd.log from your boot and I will take a look at it to see if I can find the issue.

Also, after you pull the dta2sd.log, run a2sd sysinfo and pull the dtsysdump.txt...send me that as well.

E-mail address: rtkirton@gmail.com

UPDATE: I just loaded the 08-18-2010 nightly build of CyanogenMod and RC3 is working correctly....though it did rebuild the dalvik-cache with the update package (guess there was a difference between nightly and CM RC1).

UPDATE 2: Both RC3 packages work as designed on Cyanogen Nightly Build.
[Desire Android Development] gapone:
I will try to install next nightly and if It does the same thing, I will send the logs for you. Thanks for quick answers...
[Desire Android Development] tkirton:
I'm starting to see issues with CyanogenMod nightly builds...the build is forcing dalvik-cache to go to the /cache partition, overriding any setting for Dalvik-cache you set for Apps2SD.

I have an interim release that will force Darktremor Apps2SD to take control of the dalvik-cache again: http://www.darktremor.info/files/a2sd/dtapps2sd-2.7.5-rc3a-update-signed.zip. A new command (a2sd cmpatch) forces the dalvik-cache to conform to Darktremor settings.

This is a quick-and-dirty fix and the build has only been through minimal testing, so there could still be bugs with the configuration and it is also possible that this won't work (I did successfully lock CyanogenMod during boot to the point where I had to flash a completely different rom for things to work...not sure how I did that.)

It is also possible that none of this is an Apps2SD issue, since anything that is considered a nightly build would be automatically assumed as unstable. I'm still trying to figure out what happened with the lock issue (I couldn't get control, so it either locked on kernel or init.rc). But, until it is proven otherwise, I'm going to run on the assumption that something in Apps2SD is causing a bad interaction .
[Desire Android Development] typhex:
with the new cyanogen nightly build i get stucked on white HTC boot logo. using RC3c
[Desire Android Development] tkirton:
CyanogenMod nightly builds are beta products and are constantly changing. Therefore, there's no guarantee that Darktremor will work with the latest nightly builds. For that reason, support is limited for CyanogenMod nightly builds.

With that in mind, I would erase the dalvik-cache and see if that works (wait a few minutes before declaring it not working...the dalvik-cache on CyanogenMod can take a few minutes to rebuild).
[Desire Android Development] ideasman69:
hey guys... im having some problems getting this going.

i've installed a clean OTA 2.2 rom that has been both rooted and deodexed. Nothing else has been done to it and the only thing i need is apps2sd.

i've downloaded the zip file, flashed it via clockworkmod recovery. after rebooting and starting up android, all apps still get installed to the internal memory.

i reboot the phone and jump into recovery. running the a2sd check command tells me that all apps are being installed to internal memory.

i then ran a2sd repair which configured the symlinks and the a2sd check command told me that apps will be installed to the sd card.

rebooting the phone then led to a constant boot loop. is there something simple i'm missing here? i've followed tkirton's guides on installation and usage but can't figure this out.

cheers.
[Desire Android Development] fakts13:
i believe you need to patch the init.rc file unless the rom comes with one that works with dtapps2sd. otherwise the only thing you'd be able to accomplish is putting dalvik cache on sd
[Desire Android Development] ideasman69:
awesome, thanks mate.. do you know if there's a guide for what to put in it?

i've grabbed the file off my phone.. just not sure what to put in it.
[Desire Android Development] fakts13:
http://xdaforums.com/showpost.php?p=7021331&postcount=4

not exactly the easiest thing to do but i think you should be able to find the necessary help here if you run into problems.
[Hero CDMA Themes and Apps] abadasstanker69:
Sorry about the first post. I was wondering where the png files are located in the rom so I can start theming
[Hero CDMA Themes and Apps] abadasstanker69:
If this has been addressed sorry. I searched but didn't find it. If it's been addressed please point me in the right direction. Thanks
[Hero CDMA Themes and Apps] Papa Smurf151:
Ull find all the PNG in the individual apps in the system/app, system/framework, and data/app.
[Hero CDMA Themes and Apps] abadasstanker69:
Thanks bro! All I see is apk files though. Where are the images?? Also, is there anything specific I have to do in order to export/import the files in Photoshop? I read something somewhere about a .9 PNG or something like that....what does this mean? BTW great work on your theme! It looks awesome! I love it!
[Hero CDMA Themes and Apps] abadasstanker69:
Ok I'm a douche bad. lol I renamed the apk to .zip and extracted with winrar. Now I'm in to where I want to be! I'm looking for the little android guy when you make a phone call but, I can't seem to find him in the HTCdialer.apk. Am I looking in the wrong place? Thanks again for the help!
[Hero CDMA Themes and Apps] daPorkchop:
They are in the apk's.

http://developer.android.com/index.html

Good luck.
[Hero CDMA Themes and Apps] abadasstanker69:
Ok found the little droid man! This is gonna be awesome!! Any more useful places I should mess around in? This is gonna be FUN!!!!!!!
[Hero CDMA Themes and Apps] abadasstanker69:
Ok so I have edited some files and rezipped them. Now do I flash the updated files through recovery or do I have to rename it to .apk and stick it in the rom and re-flash?
[Hero CDMA Themes and Apps] Irisht:
I may be wrong but I have done the same thing, all I did when I was finished was push them via adb to their respective places and then reboot and it worked fine for me. Nandroid before you push so if it boot loops you can recover. Then the easiest thing at that point would be to save your work in the ROM you modded, push to sd root, wipe and flash it. I am creating a themed version of Darchoid 2.7 but taking my sweet time as I dont have a lot of it to begin with.
[Hero CDMA Themes and Apps] jerry43812:
For my HTC Keyboard modifications, I just dropped my new images into the APK that was open in 7zip and pushed it to the /system/app/ dir and launched the keyboard, and BAM, my new keyboard.
[Hero CDMA Themes and Apps] daPorkchop:
You have to sign it too. If you want to flash it. If you wanna just push it through adb then then put your edited .apk in AndroidSDK\tools and push it.

Go to command prompt:

cd C:\android-sdk-windows\tools
adb remount
adb push xxxxx.apk /system/app/
exit

C:\android-sdk-windows\tools is assuming thats where your sdk\tools folder is

xxxxx.apk is the name of the .apk

/system/app/ is assuming that's where you got the .apk from
[Hero CDMA Themes and Apps] abadasstanker69:
Thanks for all the help guys. I appreciate it but, I was attempting to make an update.zip so people could then flash them once I complete them. I like to make things idiot proof ;)

So I did some looking and found an autosigner. Problem is, now it wants boot scripts? WTF? I know I could push them through adb and simply tell others to do the same. I was just wondering if there was an easy way of doing this? I'm currently using avabox. Thanks again guys!!
[Hero CDMA Themes and Apps] Papa Smurf151:
Just use a mod or update.zip any will do and add ur files and delete the originals in the zip. Keep the meta file and such. Then u can autosign with avabox. It gets tricky with scripts when making a rom. The update.zip script is very basic
[Hero CDMA Themes and Apps] kyouko:
Check This Out

You can just take one from a working zip if you want

Otherwise you will be making a file (i use notepad++) called "update-script" *notice-there is no file extension like .txt or anything*

In general they ususally just have:

show_progress 0.1 0

copy_dir PACKAGE:system SYSTEM:

show_progress 0.1 10

(but may be different depending on where you want the zip's contents to be put in)

Which will be placed into a folder directory META-INF/com/google/android/update-script

You can also add things such as:

delete SYSTEM:app/contacts.apk
*or whatever you want deleted*

After you make the update-script, just sign it and flash

See my attachment for a template
[Hero CDMA Themes and Apps] abadasstanker69:
[/QUOTE]You can also add things such as:

delete SYSTEM:app/contacts.apk
*or whatever you want deleted*

After you make the update-script, just sign it and flash

See my attachment for a template[/QUOTE]

What would be the purpose in doing that? Would it actually delete people's contacts if they flashed my theme? That's kinda cool but, I'm not trying to be a **** like that! lol :eek:

Also, are you guys referring to an update.zip that's all ready out as in a theme file? Or as in a rom? I understand I can use the work that's all ready there and I actually tried that. I zipped the file back up.Then signed with avabox. Renamed it to .apk. Stuck it back in the rom. Attempted to flash and got the boot script error:confused:
[Hero CDMA Themes and Apps] kyouko:
haha i just used contacts.apk as an example, it could be anything you wanted really. But its generally only used for when making an update.zip for boot screens.

And yes, you could take an already existing zip... but i was a little confused as to what you were doing sorry.

Correct me if I'm misunderstanding you again lol, but you're editing images within .apks and want to make a flashable-update.zip once you finish?

Easiest way, as stated before would be to use 7-zip.

Open the .apk Directly with 7-zip (no renaming the .apk to .zip or anything) and drag the replacement images into the .apk - overwriting the older images

Test it by pushing the apk to your phone, if it works without any problems great :D

If it doesn't then use something like Apk Manager to extract the apk/edit the files/and zip them back up < generally what I do

Put the .apk into the apps folder in my "template update.zip" file

Delete the framework folder and readme.txt file

Sign the .zip

Flash
[Hero CDMA Themes and Apps] abadasstanker69:
LOL I really appreciate the help! You guys kick ass!!!! BUT I tried this method MINUS the renaming part and it didn't work. Sooooo....I'm assuming the renaming caused the issue.

Also, I was using winrar. I read somewhere that 7zip should be used instead of winrar but I just don't think this should matter considering the compression method is no different. Am I wrong? Also, will my theme have to vary from rom to rom? If I create this theme for people will I have to specify what rom I'm on?

Thanks again SOOOOOOOOOO much for the help guys...I know working with noobs can be a headache. I did it in the WinMo world for YEARS till I came to the "Dark Side" ;)
[Hero CDMA Themes and Apps] Papa Smurf151:
Yes 7zip works better for theming and roming. I tried winrar and it was a pain in the ass.

Yes u will have to specify which roms it will work on. Files on darchdroid r different than our 2.1 roms and so forth. So they wont work right.

Download avabox and use the signing tool in there to sign ur zips.

Make sure in ur zip if ur editing an app it's in the right place...ie system/app or system/framework or data/app. Then make sure ur Meta file is in there. After that sign it and then u can change the name and flash it
[Hero CDMA Themes and Apps] abadasstanker69:
I'm such a freaking noob....what's the meta file for? This seems like alot to do for a theme :/