**** BEGIN LOGGING AT Wed Nov 12 02:59:58 2008 Nov 12 06:43:37 hello channel Nov 12 06:46:17 can anyone in here speak "android source build" language? Nov 12 06:48:10 I speak just a tiny bit but I'm not a native speaker... Nov 12 06:49:09 yeah i am not a native speaker, just a slightly frustrated one :) Nov 12 06:50:22 what kind of problem are you bumping into? Nov 12 06:50:41 basically i am trying to debug the touchscreen input that my touchscreen is giving to android. so i was touching frameworks/base/services.. i am curious as to what is the minimal rebuild i have to do to after i touch one of the java files Nov 12 06:51:17 I tend to trust the build system on those. A plain old make at the root gets it right most of the time. Nov 12 06:51:37 yeah it also takes a really long time.. sigh Nov 12 06:51:48 that def. work, doing it at the root Nov 12 06:51:53 what kind of machine do you have? Nov 12 06:52:05 vm... Nov 12 06:52:08 yes my fault Nov 12 06:52:15 what is your compile time Nov 12 06:52:34 when you issue a make and it just has to go through the tree and see if anythign has changed Nov 12 06:52:42 from the open-source tree, 24 minutes for a full clean build, but I'm running MacOS instead of linux so I know I'm losing a fair bit here. Nov 12 06:52:56 yeah.. Nov 12 06:53:05 how about for a tiny partial build Nov 12 06:53:11 say having touched one file Nov 12 06:53:17 and issuing a make at the top Nov 12 06:54:04 1 file in the framework (i.e. start by the java:framework task): less than 10 minutes for a full android (that includes the non-open-source apps), with only the open-source apps that'd be faster. Nov 12 06:54:29 For a single app (e.g. the download provider, which is my domain), about 10 seconds. Nov 12 06:54:48 that makes sense.. Nov 12 06:55:04 so internals just take a while to compile/dependency check/black magic itself Nov 12 06:55:33 well, if you touch the framework, dependencies will cause every single app to be rebuilt. Nov 12 06:56:13 right.. Nov 12 06:56:52 the confusing point for me is that when i touch a file in services. if i mm at that level it copies a new services.jar to the correct output directory Nov 12 06:57:29 except as far as i can tell android still behaves as it did before Nov 12 06:57:42 I'm not familiar with mm, never used it. Nov 12 06:57:52 got it Nov 12 07:57:22 yo if anyone needs an app idea, gpg encryption for messaging would be hot, plus file encryption/safe Nov 12 08:00:15 gpg is er, wrong Nov 12 08:00:22 not a good fit Nov 12 08:56:57 some even hacking the g1 ;-) Nov 12 08:57:27 oops Nov 12 14:37:09 hi, I'm still not clear on the activity lifecycle... I have activity 1 -> activity 2. calling finish() on activity 2 pops back to activity 1. is activity 2 suspended, or is it actually completed? Nov 12 14:39:17 I think it's entirely completed. Nov 12 14:40:07 If I remember correctly, activities within an application are essentially a strict stack. Nov 12 14:40:20 completed Nov 12 14:40:32 finish() doesn't call onPause Nov 12 14:43:14 yeah, I just tested it... the activity is completely done Nov 12 14:43:22 that is... next time you go to activity #2 onCreate is called again Nov 12 14:43:35 just like if you press back from activity 1 to go to the launcher Nov 12 14:43:59 if you again "click" on the app icon, onCreate is called again on teh main activity Nov 12 17:15:12 if an application is uninstalled, are the data entries it created in the database removed also? Nov 12 17:26:15 mpagano_, I believe the entire folder is removed Nov 12 17:57:56 if I have a listview and I change the background color of the list_items in the view why woult that get rid of the orange highlight color that occurs when you select an item? How can I get that back? Nov 12 18:15:16 famast: because the list selector is drawn *behind* the items by default Nov 12 19:04:27 romainguy: thanks, listSelector is exactly the keyword I needed Nov 12 19:05:27 lalala Nov 12 20:55:54 Question for the google folks: are the LOG*() macros in cutils.h synchronous? Am I guaranteed that there's no buffering between the last log I see and a crash? Nov 12 20:56:05 Sorry, cutils/log.h Nov 12 21:00:56 It's written to /dev/log/* with a synchronous write(). Nov 12 21:01:17 They won't disappear due to an app crash. Nov 12 21:02:05 system/core/liblog/logd_write.c : __android_log_write Nov 12 21:02:15 Cool, thanks. Nov 13 00:20:37 KNY: thanks Nov 13 00:36:15 mpagano, I don't remember what I helped you with, but you're welcome :) Nov 13 00:53:36 KNY: I asked if data written by app in storage gets removed when the app is uninstalled Nov 13 00:53:53 KNY: but only worded better Nov 13 00:54:37 ahh **** ENDING LOGGING AT Thu Nov 13 02:59:57 2008