好了，这里的情况：

我开发一个应用程序客户端（或试图这样做）。它需要的相同的功能内置的短信/彩信的应用程序多（如果不是全部）。所以，我认为 - 嘿！ Android是开源的吗？我可以把应用程序和修改我的需要，对吧？

所以，我发现在GitHub上code的MMS / SMS应用（出于某种原因的基础上，AndroidManifest文件，它会调用我的项目，我建，ConversationList）。但是，我碰到一个涉及进口com.google.android.mms错误吨。*包和其他几个包。

每个人都在说：这是一个私人/内部包和下载整个AOSP。但是，这样做我怎么做到这一点在Windows上，为什么我不能只是下载相应的软件包在程序中使用？

我想要做的是建立在Eclipse项目部署到我的手机上，然后修改必要code。如果Android是开源的，为什么有这么多的秘密/内部包？这是令人沮丧的。

任何意见？

所以，我发现在GitHub上code的MMS / SMS应用（出于某种原因的基础上，AndroidManifest文件，它会调用我的项目，我建，ConversationList）。但是，我碰到一个涉及进口com.google.android.mms错误吨。*包和其他几个包。

AOSP应用这样被设计为构建为固件图像的一部分，而不是作为独立应用程序

但是，如何做到这一点在Windows

最有可能的，你不知道。 Cygwin的可能工作。更有可能的是，你需要使用OS X或Linux，如在VirtualBox中运行Linux。而构建的结果不会对任何运行，但由于您使用更换固件的设备上固件版本的部分。

为什么我不能只是下载相应的软件包在程序中使用？

由于该应用程序被设计为构建为固件图像的一部分，而不是作为独立的应用程序

我想要做的是建立在Eclipse项目部署到我的手机上，然后修改必要code。

随后发现，旨在建成一个独立的应用程序作为起点的项目。或者，关于修改你要使用的工作作为一个独立的应用程序的项目，由剥开一切取决于事情是不是在应用程序本身的功能性的工作。

如果Android是开源的，为什么有这么多的秘密/内部包？

他们不是秘密。它们是固件的一部分。

例如 - 因为你似乎是熟悉Windows - 这是完全可能的，就像控制面板应用程序不设计为独立于Windows操作系统构建的。如果你能下载源$ C ​​$ C到Windows，并试图加载控制面板到Visual Studio，它绝对有可能的，你无法创造一些独立的 CPANEL.EXE 只是通过一个项目文件。相反，你需要使用一个自定义的Windows操作系统的构建过程，以建全的操作系统，其中将包含一个 CPANEL.EXE 将在操作系统中的内置版本上运行

大多数AOSP应用程序以这种方式工作。有些已经分叉创建独立的应用程序 - K-9邮件来自AOSP电子邮件应用程序的早期版本。我不知道是否有人曾与股票AOSP消息应用程序，这样做还是不行。

Okay, here's the situation:

I'm developing an application for a client (or trying to do so). It requires much (if not all) of the same functionality as the built-in SMS/MMS application. So, I thought - HEY! Android is open source right? I can take the application and modify to my needs, right?

So, I found the code on github for the MMS/SMS application (for some reason, based on the AndroidManifest file, it calls my project I built, "ConversationList"). But I get TONS of errors involving the import com.google.android.mms.* package and a couple other packages.

Everyone keeps saying "it's a private/internal package", and "download the entire AOSP". But, HOW do I do this on Windows, and WHY can't I just download the appropriate packages to use in the program?

ALL I want to do is build a project in Eclipse deploy it to my phone, and then modify the necessary code. If Android is open source, why so many secret/internal packages? This is frustrating.

Any advice?

So, I found the code on github for the MMS/SMS application (for some reason, based on the AndroidManifest file, it calls my project I built, "ConversationList"). But I get TONS of errors involving the import com.google.android.mms.* package and a couple other packages.

AOSP applications like this are designed to be built as part of a firmware image, not as standalone apps.

But, HOW do I do this on Windows

Most likely, you don't. Cygwin might work. More likely, you will need to use OS X or Linux, such as running Linux in VirtualBox. And the result of your build will not run on anything, except as part of a firmware build that you use to replace the firmware on a device.

WHY can't I just download the appropriate packages to use in the program?

Because that application is designed to be built as part of a firmware image, not as a standalone app.

ALL I want to do is build a project in Eclipse deploy it to my phone, and then modify the necessary code.

Then find a project that is designed to be built as a standalone app as your starting point. Or, work on modifying the project you are trying to use to work as a standalone app, by ripping out all the functionality that depends upon things that are not in the app itself.

If Android is open source, why so many secret/internal packages?

They are not "secret". They are part of the firmware.

For example -- since you appear to be familiar with Windows -- it is entirely possible that "apps" like Control Panel are not designed to be built independently from the Windows OS. If you were able to download the source code to Windows and tried to load Control Panel into Visual Studio, it is eminently possible that you could not create some standalone CPANEL.EXE file just via that one project. Rather, you would need to use a customized Windows OS build process to build the whole OS, which would then contain a CPANEL.EXE that would run within that built version of the OS.

Most of the AOSP apps work this way. Some have been forked to create standalone apps -- K-9 Mail came from the early version of the AOSP email app. I have no idea if anyone has done this with the stock AOSP Messaging app or not.