yashsingh1/xdaforums huggingface dataset:
[Android] mariosnc:
I tried several times to cook a Hero rom with app2sd without success. Every time i build a rom it doesn't boot. I tried to logcat during first boot but logcat doesn't seem to work. Without app2sd enabled i managed to build my rom and it is working perfectly. Is there anything i must do in order to get it working right?
[Android] keratos:
Got it! Just for anyone watching this thread...

http://developer.android.com/guide/appendix/install-location.html#ShouldNot

One could examine the manifest files in the APKs to determine if the APK can be installed into external storage (i.e. does not include the android:installLocation "internalOnly" directive).

Alternatively, 'engineering judgement' could be applied to assess whether the app contains functionality that is unlikely to affect the device when SDcard is inaccessible. For example, if the app contains widgets that are used on the home screen, we probably do not want to install that to external storage, because when the phone is connected via USB, the SDcard may well be inaccessible and the widget will be lost.

dsixda: Could your scripts be updated so that they check whether APKs in /system/app can be moved to /data/app and whether APKs in /data/app should really be in /system/app ???
[Android] capychimp:
am i stupid when i click the download link i don't have any kitchen to download on the page? just the cygwin
[Android] pendo:
in a quickie search I didn't specifically see the answer to this...

I'm guessing the reason why I'm getting a sed error is that the original sed's path is in usr/bin, which is in front of usr/local/bin in my path. So if I just type sed --version, I'm caling the wrong sed. Of course it works fine if I specify /usr/local/bin sed.

So what should I do? move the other sed somewhere else? I've never used it, but don't know if some other program might.
[Android] dsixda:
No, that's up to you to decide what goes in data/app. I don't want to spend time doing that - as there are infinite rules that could apply.

The first link in that URL has a folder called "dsixda Android Kitchen" ;) Click on that.

Please read the FAQ - I have clearly explained how to get sed working on Macs. Try it out.
[Android] pendo:
Pardon me, but I did read it, and of course re-read it after I noticed the issue. What I didn't see was if there was an issue of adding this to my path variable BEFORE usr/bin.

It's all good, I just renamed the "stock" sed command so that gnused is the one called.
[Android] mercury700ir:
I tried to find my answer from the previous posts but I can not find anything usable for me...

DSIXDA; I enabled A2SD+ from your kitchen in my rom, should I do anything else than just adding the A2sd from kitchen to activate it..??

I've tried many kitchen's and roms but I can not use A2SD, how can I activate it with this kitchen??

any body has any offer..??

-----------------------------

Oh; I forgot to tell, THANK YOU so much for your great kitchen.. ;)

I like it very much...
[Android] dsixda:
Wasn't intending to sound mean in my reply :P ... Now I see what you meant in your original email. I am glad you got it working.

Also, as I explained in the FAQ, if you put the /usr/local/bin ahead of the current PATH then it should use the correct sed (unless you have defined the PATH again later). I don't know if you followed that.

Just use your common sense guys - I have given instructions to get you up and running but please don't expect me to know everything about an OS.
[Android] dsixda:
Use option 16 and follow the descriptions. You must format EXT3 partition in your SD card.
[Android] keratos:
Yes,agreed!

I had an inclination this may be the case.

I do not feel it would be impossible to implement such functionality, but definitely agree it would require some intelligent programming. Not sure that would be a waste of time though ;)

Thanks for taking time to respond anyway.
[Android] pendo:
My apologies...kinda took it the wrong way. My main concern was if something else was using it. After a little bit of checking, I felt safe putting it aside for the time being.

I have some other questions but ill wait til I can dig through the thread a little bit more.

Thanks
[Android] capychimp:
LOL was too tired sorry man ;)
[Android] keratos:
Apps not installed to SD

DSIXDA:

I Enabled /data/app and A2SD.

Placed 20 apks in /data/app under Kitchen.

Built and flashed ok.

But all the apps are in /system/app. The 'Move to SD' card option is available.

Should they not have been there in the first place? If so then which file/script is responsible please and I'll check. Thanks
[Android] dsixda:
Did u use the default Apps2SD or the run-parts method afterwards?
[Android] keratos:
If you mean the apps2sd from the menu, then Yes!

What is run- parts?

Tia
[Android] dsixda:
It's an option added to Apps2sd in version 0.91. If you were using an older version of the kitchen then I don't know why you are having that problem.
[Android] puertoblack2003:
hey dsixda,

did you change anything in the deodex folder? I'm trying to deodex the samsung captive dump the framework is complete, but the app is not and the error is:

error: WriteandGo.odex not found

error: baksmali.jar not found

this is the first i encounter all other are fine
[Android] dsixda:
No I haven't changed anything there. Can u send me a link to the ROM? If you don't know why it's failing then i'll try to take a look this weekend. Thx
[Android] puertoblack2003:
here ya go http://xdaforums.com/showthread.php?t=730226 i tried the 1.2.3 v and it worked but partial not a full deox
[Android] mercury700ir:
Dear DSIXDA;

I have a question about the environment of kitchen that have to installed,

does this latest version work on other linux distributions like openGEU ( Looks cool and very nice OS), or debian based systems or other versions of UBUNTU ??

Because i heared that if we install the kitchen on any other OS than UBUNTU 9.xx it does not work, but in that moment we aere at version 0.8 version of the kitchen..

----------------------

And another question is, would you please tell us about the new feature you add to 0.91 A2SD..???
[Android] keratos:
dsixda:

Ok, so d/l 0.91 and now it seems to get a bit further,until I receive an error in recovery mode whilst flashing.

su is in /system/bin/su within the [created] ZIP file in the OUTPUT_ZIP folder.

Any ideas?
[Android] dsixda:
1) Read the FAQ in post #3 for my comment about other Linux

2) Read the Release Notes in post #2 and search if necessary if you don't understand the feature. Explanation about run-parts is also given when u run apps2sd option - it has to do with being able to run scripts from /etc/init.d
[Android] dsixda:
dev/tty0? I have no idea, can't really help you with that. I am not an expert on Android, I suggest you search. Sorry
[Android] keratos:
dsixda .... That is a bizarre response given that the error relates to the "su" command, and that the error is in the update-script file within the zip file created by the scripts ... These are your scripts ?? they run on linux? how bizarre.
[Android] dsixda:
Come on guys, I was up at 12am during my vacation looking at your log file, give me some slack. I'm busy looking at two other problems at the same time. Please be more respectful.

/dev/tty0 is the error i saw at the beginning of your log file. If you are talking about another error then be a bit more specific and quote it - help me out without forcing me to dig further.. because I am busy enough as it is. I cannot read your mind. ;) Thank you
[Android] dsixda:
Puerto, I'm not having the issue that you explained earlier. HOWEVER, this problem might occur if you had saved a script file (e.g. do_deodex_file) WHILE the same script is running.

I am currently updating the do_doedex_file with the Samsung JAR dependencies, as I notice your odex files generate some errors.
[Android] keratos:
Ahhh.damm. awfully sorry dsixda please accept my apologies. No disrespect intended.i am sorry

could it be something to do with the "simlink toolbox .... /bin/su" line in update-script ?d

Darren
[Android] dsixda:
Why does your update-script have the line "symlink toolbox SYSTEM:bin/su"??? The su binary should never be part of toolbox. Where did you get this ROM?

My kitchen has nothing to do with it. :confused:

E:Can't symlink /system/bin/su
E:Failure at line 49:
symlink toolbox SYSTEM:bin/su
Installation aborted.
[Android] dsixda:
I've just put out version 0.92... enjoy :-)
[Android] robocik:
Nice :)

Thanks man!
[Android] keratos:
erm, mate, may I refer you to the header in the update-script file...

#
# Generated by dsixda's HTC Android Kitchen
# xda-developers.com
#

so its not generated by you then ???

mmmm?
[Android] myn:
Just an observation about the signing process.

If you select the option to sign ALL apks, it will include the files in the /data/app directory as well. If those apps are signed with the test keys any subsequent update via the market will fail as the keys do not match.

As a suggestion, When a user chooses all, perhaps prompt them to sign all of the apks in /data/app too?

Thanks again for all of your hard work. This really is a very very solid application :).
[Android] dsixda:
You still have not answered my question. The header doesn't really prove anything. If someone created a ROM with my kitchen (the above header normally gets added to roms created from a Nandroid or shipped rom) then they could add the su line later manually. The only other thing I can think of is that you are using a Nandroid backup with a system/bin/su shortcut. I didn't however recommend the use of Nandroid backups in the kitchen, as I said in the FAQ, but it's still something I can take a look at if you tell me what you did.

The other thing that just came to mind is that I should avoid using that header altogether, as I don't have full control of what someone is adding to the update-script, so I am not necessarily "generating" that file.
[Android] dsixda:
Thanks a lot for the recommendation, there are always people asking about signing issues. I'll take a note of the changes to be made.
[Android] dsixda:
I've uploaded new version 0.93 to hopefully make both of you happy ;-)

Thanks
[Android] lpasq:
dsixda >>>

updates continually amazing! thanks for the nandroid love in v0.93.

Sent from N1...
[Android] dsixda:
This was already handled a long time ago (ie. for Nandroid backups) with fix_update_script_with_features.

Regarding your /bin/cat issue, I don't know why you got that error because that would mean you have cat as both a binary and a symlink under /bin, which shouldn't happen.

I don't want to spend more time on Nandroid backups because there are infinite possibilities and rules to look for when creating a fresh update-script. That's why I have never recommended building a ROM from them.

There's one thing I forgot to do in the last update, which was to check if files like 'cat' exist as symlinks in both /bin and /xbin (such as busybox files) --

e.g. If the /bin file also occurs in /xbin (e.g. su) then the update-script toolbox entry is not created in /bin, because files like 'bash' and 'su' are not toolbox files. However, if the /xbin file is not a binary but instead a busybox

symlink

(e.g. cat) then the update-script toolbox entry should still be allowed to be created in /bin. Currently the latter statement is not handled in the kitchen.

EDIT: I'm uploading a new version of 0.93 with the small change I mentioned in the previous sentence.
[Android] Kanzie:
Actually, I think I've had a similar problem earlier - either CM6 or Azure (legend port of CM6) had su as binary in /system/bin, but the add root step in the kitchen places su in /system/xbin and create a symlink to /system/bin (or something like that).

I haven't played with the kitchen for quite a while, now that I've a rom that I like, so I wouldn't know if anything had changed.
[Android] dsixda:
The problem was with the "symlink toolbox" command, which wanted to created a system/bin/su symlink, and not about the 'add root' option, which creates a regular symlink for system/bin or system/xbin.

There's no problem with the su binary during regular kitchen operation; it just was a problem when people used a Nandroid backup for cooking, which I don't suggest as a reliable option anyway.

I think the issue you are talking about was one I fixed several weeks ago.
[Android] juansuandi:
hey, thanks again for this great kitchen. today i try 0.91 versions. and get an error. i use it on desire ROM.

i get error on dtinstall.launch, cannot run DATA:dtinstall.launch.

its say not supported for run_program because it was non-package.

i then try to modified the run_program from DATA:dtinstall.launch to run_program PACKAGE:dtinstall.launch on update script. surely i move the dtinstall.launch first to another folder. but i get error status. when i try to remove it, i get success on flashing the ROM but a2sd is not run correctly when i check on adb logcat.

any idea about this? thanks so much dsixda for this kitchen.
[Android] capychimp:
dsixda, in your deodex script you copy the dex file into the apk, is it possible for you to creat a script taking a different file, from a folder into an apk? in a batch job, i have 84 folders each with a file called resources.arsc which should be copied into the apk's of same name as the folder they are in, it's alot to write in a post here, but just curious if you could hint me in someway to make a script to do it
[Android] dsixda:
I did a Google search... that message occurs due to an issue with the recovery menu image you are using. Flash another recovery image and try the same ROM again.
[Android] dsixda:
You could check the deodex scripts under the /scripts folder for ideas on how to change an apk.

This is stuff outside the bounds of the kitchen though. Spend some time to learn how to write shell scripts, it is actually not that hard. ;) Don't rely on others to do the work for you... learn and have fun :)
[Android] keratos:
I have to say that this is incorrect! As I said above, your script tests for symlinks only. It [the script] will fail if regular files and executables exist. Its a simple enough change to make and I provided you with an appropriate suggestion.

I dont understand what you mean here. Are you suggesting there can be a binary and symlink under the same inode entry. That seems to be what you are saying and this is impossible. Again, the answer is very simple and the same as above. The /bin/cat /bin/su and other /bin files exist as EXECUTABLES. Your script wants to create symlinks from these files to toolbox. Your script fails because they already exist. Its a SIMPLE change my friend and I've provided the correct code.

Why so. The [current] issue is that your update script wishes to symlink to toolbox. Thus the possibilities are not infinate and the rules are simple: If 'the file' exists, leave it or replace [delete] it with a symlink. 'The file' = all instatiations of the implemented files in toolbox. The rules are not infinate because you have the list of files in your default_symlinks file - you need only check for these.

This the principle I am attempting to convey, albeit you have scoped to busybox. The principle is the same for busybox as it is for toolbox, in that there are a number of files implemented by busybox and a number of files implemented by toolbox. The files are known (thus not infinate) and the rules for checking are simple (thus not infinate).

Same PRINCIPLE albeit different scenarios.

Tell you what my friend, if you do not wish to implement these features - which will only serve to increase the excellence and functionality of the toolset - then I plan to fork my own kitchen in competition which will do all of this and more. I dont want to re-invent the wheel and would much prefer to contribute to the success of your toolset. I would certainly implement [in my kitchen] features such as: kernel options (CPUgov, scheduling etc), home screen options (ADW, launcer, sense etc.), goolgle-apps (withdrawn from market i.e youtube), fonts, themes and so on. I'd probably make it an executable too in order to simplify and for speed.

Over to you.
[Android] dsixda:
Not necessarily, it will not fail. The other thing is, you are suggesting using an update-script with default toolbox entries, which is actually what I had done in the past but it did not work for all cases, partly because not all ROMs use the same toolbox or support all the entries.

In addition, the Nandroid backup uses the .img file format which the shipped ROMs also use -- they both call the same fix_update_script procedure. If I used a default set of update-script entries when extracting a shipped ROM, then it will be different from what the actual shipped ROM started off with, and I don't want to do that. What I did is, for every symlink that is removed from the shipped ROM, it is replaced with the same toolbox entry in the update-script, not with some default toolbox lines.

I have refined this method for many months and am not eager to change this behaviour, for fear of breaking other functionality. I have never recommended making a ROM from a Nandroid backup, and personally, I just want to leave it as is because it's not broken, and I have many other things to do (family, hobbies, work, etc.). Remember, I'm just one guy.

It seems you are taking this all personally, I would suggest you relax and not worry about it... it's just a phone. The majority of the kitchen has been achieved through user input, it's not like I am ignoring you.

LOL, good for you, I'm not here for competition. XDA-developers is not about competition, it's about sharing information. I'm not looking for fame or credit, I'm here to help others (and myself) learn about Android.

Anyways... I am not good at arguing, and this thread is not for arguments.. It is a help and support thread for the kitchen. It seems this thread has degenerated in the last couple of weeks, probably because the more I work on it, the more people take it for granted and expect more from me. If you have a problem with me then don't use the kitchen, simple as that.
[Android] nbetcher:
EDIT: nevermind - someone else told me no other action should be needed other than putting it into /data/app, but for some reason that hadn't worked for me at the time.

I have a question: this script has the option to "Enable /data/app functionality" however I cannot find a way to make this useful. I put apps in /data/app and it does not install the applications so that they show up in the launcher. Putting them into /data/app is not sufficient from what I can tell and would require making a script to add the package's info to /data/system/packages.xml.

Can someone elaborate on this process?

Thanks!
[Android] myn:
Excellent :)

Thank you.
[Android] :
Feature Request : last time i used 0.73 so i don't know if it's the newest one, would have to check, BUT

- Ability to unpack/repack an .apk (no theming, just the same as we do with the kernel images)

- Odex all system libraries/apps. Before you go protesting, on Sense roms, this saves about 80MB of space on /data, which SHOULD be in /system, but because of deodexing land on /data and prolong first boot.
[Android] dsixda:
I don't know how to unpack and repack an apk without getting errors with signing and compression after it's flashed.

Also I don't know how to odex. You can odex a ROM with dexopt-wrapper running on your device, I think..
[Android] listyb01:
Hey dsixda, I know a lot of "adding theme" questions have been asked and I know that you don't really get involved in the theme aspect of ROM building but I have a request, if it would even be possible.

Is there any way to add a "theme porting" script to the kitchen?

Danesmh90 has written a script here: http://xdaforums.com/showthread.php?t=737526 but it is for windows only.

Would be great to see something like this in the kitchen.

Thanks!
[Android] dsixda:
I don't know, it looks too involved, and at this point I don't want to do that much work and testing and then making sure it works for all 3 platforms. Don't really have time these days other than minor fixes... it's hard to do with a family. Hope you understand.

I also don't think the time and effort is worth the trade-off (i.e. the # of people actually using it). Someone posted a Linux version for it anyway, so just search that thread.
[Android] listyb01:
I understand completely. Thanks for the consideration and keep up the good work.
[Android] dsixda:
I've uploaded version 0.94, which includes some bug fixes. Thanks to those who provided the feedback.
[Android] Quetzecotyl:
Today, I am trying to dump the Ace rom with the latest kitchen. Using .53, I was able to extract several Supersonic, Incredible, and Desire ROMs, but since updating to .94 a few hours ago (complete reinstall of the kitchen), I continually get an error that states there is a segmentation fault of some type when extracting the system.img.

After redownloading the rom a couple more times from different sources and seeing the hash is identical everytime, and reinstalling the kitchen using the custom cygwin again, I still get this segmentation fault error when the system.img is extracting. Here is an example of the error (I think sometimes the line ###: #### Segmentation fault ####s are different, but I haven't been keeping good track):

Extracting contents of system.img ...
scripts/img_files_to_working_folder: line 100: 3060 Segmentation fault (core dumped) ../../tools/unyaffs_files/$unyaffs_file system.img

Inside the working folder/system, a file is left called unyaffs.exe.stackdump. Here are its contents:

Exception: STATUS_ACCESS_VIOLATION at eip=004010A0
eax=E2844001 ebx=00000002 ecx=A3A02000 edx=00C781EA esi=612286F2 edi=00000000
ebp=0022CD08 esp=0022CCD0 program=C:\cygwin\home\Admin\kitchen\tools\unyaffs_files\unyaffs.exe, pid 3060, thread main
cs=001B ds=0023 es=0023 fs=003B gs=0000 ss=0023
Stack trace:
Frame Function Args
0022CD08 004010A0 (612285AC, 00000000, 611F0108, 00401323)
0022CD38 0040139F (00000002, 61228684, 00C500F8, 610049BE)
0022CD68 61006E73 (00000000, 0022CDA4, 61006720, 7FFDD000)
End of stack trace

Seems like a problem with unyaffs.exe and not the ROM itself? Any advice would be appreciated; I'll try to dump the rom again with the older kitchen version.
[Android] dsixda:
Solution - although it probably only works in Linux:

http://xdaforums.com/showpost.php?p=8199509&postcount=10

Don't waste your time with an older buggy version.

I haven't tried using the new ROM yet though.
[Android] warriorvibhu:
Also My friend i wanna suggest you a fix for custom bootanimation in your kitchen :::: many devices have bootanimation here /system/media folder and not data/local folder..

One more thing.. its never too late to appreciate.. I loved your Onyx Roms for Elf... if my device had not died i would still be running your Roms on it... :) ..
[Android] dsixda:
Thanks for the comments..

Regarding the boot animation, yes I know, stock ROMs don't use /data/local. We had discussed it in this thread in depth (just search the thread).

You should read this - http://xdaforums.com/showpost.php?p=7717983&postcount=1735. There are different locations for bootanimation.zip; /system/media is one of the defaults (depending on device) and /data/local is the custom location. Hope that helps.
[Android] RyanLee:
Greetings once again.

Downloaded the 3.29.651.5 OTA update that dropped for the EVO today From myn's thread.

Downloaded 0.95 of the kitchen (thanks for your continued efforts!)

Removed all instances of previous builds

Ran through steps 1-9, skipping 6 and 8

Everything shows as expected

Ran step 13 to add /data/app

The folder is created but again, for me, the check_data_app file is not

Here's the update-script after completing the steps above

Is this file no longer necessary or am I just causing more problems?

Thanks again for all your help
[Android] RyanLee:
My previous post can be disregarded unless other folks are having this issue.

I enabled /data/app only for Astro installation. To access my apps after flashing with the ability to remove it if something else catches my eye later. But, Astro works well for what I need so I just moved it to /system/app and left it at that.