| Jun 2 |  8:55 AM | 
| Mark M. | has entered the room | 
| Mark M. | turned on guest access | 
| Jun 2 |  9:00 AM | 
| Owen C. | has entered the room | 
| Owen C. | Good Morning | 
| Mark M. | howdy, Owen! | 
| Owen C. | So
i'm finding the tutorials a great help, i've been working through them,
however i'm still unable to open up the app on my device | 
| Mark M. | what OS are you running? | 
| Owen C. | windows 7 | 
| Mark M. | that could be a problem | 
| Mark M. | this was a Nexus One, right? | 
| Owen C. | yes | 
| Mark M. | I seem to recall there are driver issues with that combination | 
| Owen C. | hmm ok | 
| Mark M. | let's do this | 
| Mark M. | pop open a Command Prompt | 
| Owen C. | ok | 
| Mark M. | cd into the tools/ directory in wherever you installed the SDK | 
| Mark M. | and, with the Nexus One plugged in, run "adb devices" (sans quotes) | 
| Jun 2 |  9:05 AM | 
| Mark M. | you should get something like: | 
| Mark M. | |
| Owen C. | the sdk would install in a .android folder? | 
| Mark M. | it's a ZIP file, so I don't know where you unpacked it | 
| Mark M. | there is an .android folder in your user area, but that | 
| Mark M. | is not where the SDK is installed | 
| Owen C. | ok | 
| Owen C. | i've found it | 
| Owen C. | what do you mean cd? | 
| Mark M. | I mean the cd command | 
| Mark M. | or chdir if you like to use the longer form | 
| Mark M. | I'm guessing you haven't used the Command Prompt much on Windows machines | 
| Owen C. | nope :) | 
| Owen C. | i'm just googling it | 
| Owen C. | i'll be there in a second | 
| Jun 2 |  9:10 AM | 
| Owen C. | hmm | 
| Owen C. | so i'm getting an error that it isn't a recognizable command | 
| Mark M. | never mind | 
| Mark M. | on a whim, in the Command Prompt, just type "adb devices" (sans quotes) and press <Enter> | 
| Owen C. | yeah same thing | 
| Mark M. | OK | 
| Owen C. | it just isnt recognized | 
| Mark M. | the problem is, I don't use Eclipse and don't own Windows 7 | 
| Mark M. | where did you install the SDK on your PC? | 
| Owen C. | just a random folder | 
| Mark M. | please tell me the random folder | 
| Owen C. | its in my share folder | 
| Owen C. | C:\Users\Owen Coutts\Downloads\android-sdk_r05-windows\android-sdk-windows | 
| Mark M. | OK | 
| Mark M. | type the following into the Command Prompt: | 
| Mark M. | cd "C:\Users\Owen Coutts\Downloads\android-sdk_r05-windows\android-sdk-windows" | 
| Mark M. | (and this time the quotes are important) | 
| Owen C. | alright | 
| Jun 2 |  9:15 AM | 
| Mark M. | now, type in: | 
| Mark M. | cd tools | 
| Owen C. | Yeah, it still isn't recognizing the command | 
| Owen C. | ok | 
| Mark M. | what command? | 
| Owen C. | sorry i tried adb devices again | 
| Owen C. | ok now in tools i'm getting the emulator thats on | 
| Owen C. | but i don't see my nexus one | 
| Mark M. | OK, we're getting somewhere | 
| Mark M. | shut down your emulator | 
| Mark M. | and unplug the device from the PC | 
| Owen C. | alright | 
| Mark M. | now, type in: | 
| Mark M. | adb kill-server | 
| Mark M. | then: | 
| Mark M. | adb start-server | 
| Owen C. | ok | 
| Mark M. | now, plug the Nexus One back in, wait a couple of seconds, and try "adb devices" again | 
| Owen C. | it doesn't show any devices now | 
| Mark M. | OK | 
| Mark M. | most likely, you have a driver issue | 
| Owen C. | ok | 
| Mark M. | unfortunately, I don't have great advice on how to fix it | 
| Mark M. | you can try the steps shown here: | 
| Mark M. | |
| Jun 2 |  9:20 AM | 
| Mark M. | though they are for XP and Vista, not 7 | 
| Owen C. | hmm ok | 
| Mark M. | since I haven't even *seen* 7 (I'm a Linux guy), I don't know how closely the Vista instructions will match what 7 gives you | 
| Owen C. | maybe it would just be easier to vm into xp? | 
| Owen C. | vista drivers have usually been ok for me | 
| Mark M. | if your VM solution offers some form of USB pass-through, perhaps | 
| Mark M. | I
didn't have a problem getting my Nexus One to work on my Vista
notebook, and so I have limited experience with Android device driver
problems on Windows, let alone 7 | 
| Owen C. | yeah i mean i have everything setup here it seems to be workign fine | 
| Owen C. | i guess i can't try an older version of the driver because it wouldn't have n1 support | 
| Mark M. | sorry I couldn't be of greater help on this issue | 
| Owen C. | no problem | 
| Owen C. | thanks anyway | 
| Jun 2 |  9:40 AM | 
| Owen C. | has left the room  | 
| Jun 2 |  9:45 AM | 
| Ethan L. | has entered the room | 
| Ethan L. | Hi Mark | 
| Mark M. | howdy, Ethan! | 
| Mark M. | how can I help you today? | 
| Ethan L. | Good to chat with you again. Remember me? I took the Android bootcamp in February in Atlanta. | 
| Mark M. | yes, I remember you! | 
| Ethan L. | I have a few questions regarding android | 
| Mark M. | fire away! | 
| Ethan L. | As I understand it, the Android stack is divided into the Linux Kernel, Libraries, Application Framework, Apps | 
| Ethan L. | I was able to find lice | 
| Mark M. | lice? | 
| Ethan L. | I was able to find the license for the kernel (GPL) | 
| Ethan L. | the libraries are Apache license with some parts that are more restrictive licenses | 
| Mark M. | most everything else is Apache Software License 2.0 | 
| Ethan L. | including the app framework? | 
| Mark M. | yes | 
| Ethan L. | i found some conflicting info saying that it's "close-source" | 
| Jun 2 |  9:50 AM | 
| Ethan L. | does this include the Android runtime? | 
| Ethan L. | also under Apache? | 
| Mark M. | If by the "app framework" you mean the APIs and such that you write Android apps to, no, that is not closed source | 
| Mark M. | I don't know what "the Android runtime" is, in your eyes | 
| Mark M. | let's reverse the issue: | 
| Mark M. | the only things that are NOT under Apache2 are... | 
| Mark M. | ...the kernel | 
| Mark M. | ...a few other libraries (e.g., bluez) that are also (L)GPL | 
| Mark M. | ...some drivers for some devices | 
| Mark M. | ...and some of the Google apps, such as the Market and Maps | 
| Mark M. | everything else is Apache2 | 
| Ethan L. | oh ok | 
| Mark M. | they are explicitly trying to minimize (L)GPL components, out of concern that device manufacturers might not like it | 
| Mark M. | some drivers and the Google apps are proprietary | 
| Ethan L. | so what is the control that Google has over the device manufacturers on customization of the stack... | 
| Mark M. | you don't get the Market and such unless you pass compatibility | 
| Mark M. | |
| Mark M. | CDD and CTS are key | 
| Mark M. | and are described on that site | 
| Mark M. | you don't have to ship an Android device with the Market and such if you don't want | 
| Mark M. | in that case, the compatibility stuff falls to "a really good idea" rather than "a must-have" | 
| Ethan L. | for
example, if manufacturers were to add a new library (to the Libraries
layer), or manager to the app framework. Do they have to get it
approved by Google or contribute this back to Android community? | 
| Mark M. | no and no | 
| Mark M. | so long as it does not break compatibility, Google won't quibble | 
| Mark M. | see the Evo 4G and its front-facing camera support | 
| Jun 2 |  9:55 AM | 
| Mark M. | now, I am not a lawyer, nor do I play one on TV | 
| Ethan L. | :) | 
| Ethan L. | if i add a totally new functionality that is not part of the CDD, am I still free and clear from Google and contribution? | 
| Mark M. | and
without knowing all of the licenses involved in your library and where
it attaches to Android, I cannot state conclusively that there aren't
license issues | 
| Mark M. | as far as I know, yes | 
| Mark M. | however, that's a far better question for somebody at Google | 
| Mark M. | perhaps the [android-porting] Google Group could help | 
| Ethan L. | but then i guess i'm on my own to support the new stuff in the next rev of Android | 
| Mark M. | oh, yeah | 
| Ethan L. | cool | 
| Ethan L. | changing the topic a bit | 
| Ethan L. | i
wanted to know if there's any inherent in the Android stack (besides)
apps that tie you in to google services. I couldn't find anything so
wanted to make sure... | 
| Mark M. | Well, I suspect there's some stuff below the app level | 
| Mark M. | for example, on some Android devices, you have to sign in with a Google account at activation time | 
| Mark M. | however, I'm not a firmware guy, so I don't know exactly where the Google account stuff all plugs in | 
| Mark M. | it is certainly possible to have devices sans Google accounts -- see the ARCHOS 5 Android tablet | 
| Mark M. | however, I don't know if you can pass CDD/CTS | 
| Mark M. | I haven't delved into CTS myself, since it's rather big | 
| Mark M. | and I only recently skimmed the CDD document and forget what it said, if anything, on Google accounts | 
| Ethan L. | yeah i tried to read those docs and it's so long :) | 
| Jun 2 | 10:00 AM | 
| Mark M. | particularly for me, since I'm not likely to be building any Android devices very soon | 
| Mark M. | I don't have enough LEGO(R) bricks... | 
| Ethan L. | i
think one of the use case i'm trying to answer would be if on the
handset, without signing in to my google account, i launch a browser
and go to Yahoo search. Will google still know about my search habit? | 
| Mark M. | if by "search habit" you mean whether Google will record the search string, I sure hope not | 
| Mark M. | after all, you don't have to use the standard Browser app | 
| Mark M. | there's Opera Mini, and soon Mozilla Fennec | 
| Mark M. | any last questions before I close this office hour? | 
| Ethan L. | just
to summarize so I have it straight: ok so from what i understand, then
modifications to the stack are permitted and doesn't require
contribution (dependent on which libraries). you can do as much as you
want as long as it satisfy CDD/CTS if you want marketplace support but
support for future releases is on your own | 
| Mark M. | generally speaking, yes | 
| Ethan L. | sweet | 
| Ethan L. | thanks Mark | 
| Mark M. | the devil, of course, is in the details | 
| Jun 2 | 10:05 AM | 
| Ethan L. | you've really helped | 
| Mark M. | no problem | 
| Mark M. | have a great day! | 
| Ethan L. | thanks you too | 
| Ethan L. | has left the room  | 
| Mark M. | turned off guest access | 
