移植到AOSP特定的硬件设备 [英] Porting AOSP to specific hardware device

问题描述

更新：在此基础上下面是以下问题：为AOSP创建特定设备树

我跟着这个： https://source.android.com/source/building.html ，并设置环境，并下载最新的AOSP。现在我wnat闪烁，它在我的特定设备，让我们说的Galaxy S2。

1. 在配置USB访问：51 android.rules，那应该怎么看？因为在上述官方教程中的每个条目如下：

   装置X // ADB协议

   SUBSYSTEM ==USB，ATTR {idVendor} ==18D1，ATTR {} idProduct ==4e12，MODE =0600，OWNER =用户

   装置X // FASTBOOT协议

   SUBSYSTEM ==USB，ATTR {idVendor} ==0BB4，ATTR {} idProduct ==0FFF，MODE =0600，OWNER =用户

   但在很多地方，我发现这一点：

   SUBSYSTEM ==USB，ATTR {idVendor} ==0502，MODE =0666，GROUP =plugdev

   当然，将用户添加到plugdev组是显而易见的，但仍然是：在Google`s方式有亚洲开发银行和功放独立的条目;这模式下，模式是不同...

   什么是终极测试，看看这一步工作？




2. 假设我修改code和正确的线路;配置文件我喜欢这里表示特定的设备：用于AOSP Android设备的配置。这意味着我有充分AOSP文件的目录。在 $午餐aosp_arm-ENG 的阶段应该是什么参数特定的硬件设备？




3. 现在假设我在建及放我的输出目录;编译AOSP文件。我应该如何闪我的装置？这不是从Google`s上面的教程很清楚。我preFER得到的只是为了通过CWM恢复等闪烁一个单一的zip文件。




4. 有没有办法闪烁它的硬件设备上（为了减少砖的机会）？前测试结果

谢谢，

解决方案

1. 亚行规则，使亚行通过USB工作。如果你可以通过ADB连接到您的设备，然后在亚行工作规则。您可能必须启用亚洲开发银行在设备的开发人员设置。


2. 在您同步，您可以建立您的设备AOSP。你可以选择你的午餐菜单设备。运行构建/ setenv.sh脚本。然后运行午餐。它可以让你可以选择特定的设备列表。您可以通过同步新设备的树到树添加到列表中。


3. 默认情况下，将建立您通过FASTBOOT闪system.imgs。如果您正在构建AOSP，使otapackage 将作出擦写拉链。


4. 构建将使您可以通过运行仿真器测试模拟器图像。这会给你，如果你的建筑工作的总体思路，但不会给你问候你的特定设备完整的故事。例如，模拟器建立可能会遇到，但如果你忘了添加特定的设备上正确的专有文件的生成可能无法引导。但你不太可能硬砖设备通过闪烁着system.img。

UPDATE: Based on this Here is following question: Create specific device tree for AOSP

I followed this: https://source.android.com/source/building.html and set up the environment and downloaded the latest AOSP. Now I wnat to flash it on my specific device, let's say Galaxy S2.

1. In the "Configuring USB Access: 51-android.rules", how it should look? Because in above official tutorial each entry looks like:

   //adb protocol for device X

   SUBSYSTEM=="usb", ATTR{idVendor}=="18d1", ATTR{idProduct}=="4e12", MODE="0600", OWNER="user"

   //fastboot protocol for device X

   SUBSYSTEM=="usb", ATTR{idVendor}=="0bb4", ATTR{idProduct}=="0fff", MODE="0600", OWNER="user"

   But in many places I found this:

   SUBSYSTEM=="usb", ATTR{idVendor}=="0502", MODE="0666", GROUP="plugdev"

   Of course adding user to plugdev group is obvious, but still: In Google`s way there is separate entries for adb & fastboot, and the mode is different...

   What would be the ultimate test to see if this step works?

2. Suppose I modify the correct lines of code & config files for my specific device like stated here: Android device configuration for AOSP. Which means I have a directory with full AOSP files. In the stage of $ lunch aosp_arm-eng what parameters should be for specific hardware device?

3. Now suppose I have in my output directory built & compiled AOSP files. How should I flash it on my device? It's not very clear from Google`s above tutorial. I prefer to get just a single zip file in order to flash it via CWM recovery etc.

4. Is there a way to test the result before flashing it on hardware device (To reduce the chances for brick...)?

Thanks,

解决方案

1. The adb rules are to enable adb to work over USB. If you can connect to your device over ADB then the adb rules worked. You may have to enable ADB in the device's Developer Settings.
2. After you have synced AOSP you can build for your device. You can choose your device in the lunch menu. Run the build/setenv.sh script. Then run lunch. It will have a list of specific devices you can choose from. You can add to that list by syncing new device trees into the tree.
3. By default it will build system.imgs that you flash through fastboot. If you are building AOSP, make otapackage will make a flashable zip.
4. The build will make an emulator image that you can test by running emulator. That will give you a general idea of if your build works, but will not give you the full story with regards to your specific device. For instance, the emulator build might run but if you forgot to add the correct proprietary files the build might not boot on your specific device. But you are very unlikely to hard brick your device by flashing a system.img.

这篇关于移植到AOSP特定的硬件设备的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！