oLUCKo

@mazz 可以认为是要统一编译环境 .
就是想做一个隔离 .
1. 在 宿主机随便折腾 , 系统搞崩了实在搞不定需要重装的时候, 不担心 需要 为 aosp 重新配置什么(安装下 docker 就好) .
2. 当然在 docker 也随便折腾 , 不用担心 搞的宿主机不稳定/臃肿 .

我也注意到 aosp 编译工具本身也有做隔离动作(没有仔细研究) .

谢谢所有参与话题的大佬们的分享 .
重点参考了 @mazz @Donaldo 目前看 效果很好 .


----

关于购买:
1. 我是 dell 官网下单(联系售前能比官网自己选配好后的价格有优惠) .
2. 体验很差 . (家用设备)售前动不动就已读不回已读乱会 , 配置细节售前客服的咨询服务还不如没有 . 因为 ta 会随意误导你 .
3. (商用设备)售前比较专业 , 有问有答 , 不知道就说不知道(会内部咨询后答复) . 没有错误信息 .
4. 是的我也沟通了 lenovo 官方售前 , 感觉就是业余 , 业余的很 .


关于京东:除了 dell 官网 都是三方销售(含京东) . 对售后不信任 .
- t/463426
- 我个人在京东自营平台也有被欺诈的经历 , 所以祛魅了 , 保持警惕 .

为什么选品牌机
1. 想要省点心
2. 我已经被低配设备折磨 6 个月了 . 不敢想象新购入的设备出什么幺蛾子 .
3. 不是说 DIY 就有风险 , 我从没试过 DIY , 担心有坑 . 不想趟了 .

----

T3680 配置如下
i9-14900K
128G RAM
核心显卡
M2.SSD(OS) + SATA.SSD(AOSP)

----

aosp13 编译资源峰值

内存峰值 42G + 85G(缓存) + 1G(Swap)
完整编译用时 (44:18 (mm:ss))

运行过程(几乎就是只做了编译工作 , 和这个文本编辑):

debian 宿主机 + ubuntu docker container
```shell
$ sudo docker run --privileged \
--add-host=host.docker.internal:host-gateway \
--memory=120GB \
--memory-swap=240G \
--cpuset-cpus='0-30' \
--name docker-ubuntu18 \
--hostname docker-ubuntu18 \
-it --rm -v /Volumes:/Volumes \
aosp-build-ubuntu18.04:1

m -j 28
```

----

使用感受
1. 对比我的 32G+i7 , 不会出现各种奇怪的错误了 , 一次成功 .
2. 编译期间极其短暂的 散热风扇轰鸣 . 坦白说持续那样的话确实很吵 . 但是心里是很踏实的 , 你听到声音就觉得它行 , 觉得它还没用全力 .

@Ayaya233 我开始操作 aosp 13 也这么想的 , 直到我做了简单修改后 , 遭遇了 oom .

@HtPM 是的 64G 打底 . https://source.android.com/docs/setup/start
A minimum of 64 GB of RAM. Google uses 72-core machines with 64 GB of RAM to build Android. With this hardware configuration, it takes approximately 40 minutes for a full build of Android and only a few minutes for incremental build of Android. By contrast, it takes approximately 6 hours for a full build with a 6-core machine with 64 GB of RAM.

@Donaldo 大佬 , 在 aosp 的高内存占用场景下 , 峰值能占到多少内存呀 ? 我没上过这么大的硬件 , 对此一无所知 .

@MacsedProtoss 个人页很喜欢 mac 的 . AOSP 编译对 X86 有更好的支持 . 所以没法考虑 arm 的 .

啊 sorry
[Precision 5860 塔式工作站 服务手册]( https://www.dell.com/support/manuals/zh-cn/precision-5860-workstation/precision_5860_tower_sm/%E7%B3%BB%E7%BB%9F%E4%B8%BB%E6%9D%BF%E6%A0%87%E6%B3%A8?guid=guid-520a5187-a27e-41eb-8d72-2a30479d1227&lang=zh-cn)
被我写成了 5680

@dankai

lunch 是 : lunch sdk_phone_arm64-userdebug


我尝试了两种方式

1. 黑屏无法启动 --> 将生成的 cache.img / ramdisk.img / system.img / userdata.img 放到 android_sdk/system-images/android-23/default/arm64-v8a 目录下 , 通过使用 sdk 中的模拟器启动 emulator . 现象是 黑屏无法启动

2. 黑屏无法启动 --> 使用 AOSP 中的 emulator 执行文件 指定 img 路径 , 第二中方式的指令和日志如下 :

模拟器启动用的这个执行文件, 日志转储可以忽略 , 以下是实际的日志内容 , 模拟器的实际表现就是 黑屏 . 没有任何其他了

$AOSP_PATH/prebuilts/android-emulator/darwin-x86_64/emulator64-arm -verbose 2>&1 | tee a /Volumes/MacOs_disk/AOSP/android-6.0.0_r6.tmp/emulator.log/6.emulator.just.aosp.content.arm64.log

emulator: found Android build root: /Volumes/MacOs_disk/AOSP/android-6.0.0_r6
emulator: found Android build out: /Volumes/MacOs_disk/AOSP/android-6.0.0_r6.tmp/build_out/target/product/generic
emulator: Read property file at /Volumes/MacOs_disk/AOSP/android-6.0.0_r6.tmp/build_out/target/product/generic/system/build.prop
emulator: Cannot find boot properties file: /Volumes/MacOs_disk/AOSP/android-6.0.0_r6.tmp/build_out/target/product/generic/boot.prop

emulator: Found target API sdkVersion: 23

emulator: virtual device has no config file - no problem
emulator: using core hw config path: /Volumes/MacOs_disk/AOSP/android-6.0.0_r6.tmp/build_out/target/product/generic/hardware-qemu.ini
emulator: found skin-specific hardware.ini: /Volumes/MacOs_disk/AOSP/android-6.0.0_r6/development/tools/emulator/skins/HVGA/hardware.ini
emulator: autoconfig: -skin HVGA
emulator: autoconfig: -skindir /Volumes/MacOs_disk/AOSP/android-6.0.0_r6/development/tools/emulator/skins
emulator: found skin-specific hardware.ini: /Volumes/MacOs_disk/AOSP/android-6.0.0_r6/development/tools/emulator/skins/HVGA/hardware.ini
emulator: keyset loaded from: /Users/tom/.android/default.keyset
emulator: trying to load skin file '/Volumes/MacOs_disk/AOSP/android-6.0.0_r6/development/tools/emulator/skins/HVGA/layout'
emulator: skin network speed: 'full'
emulator: skin network delay: 'none'
emulator: autoconfig: -kernel /Volumes/MacOs_disk/AOSP/android-6.0.0_r6/prebuilts/qemu-kernel/arm64/kernel-qemu
emulator: Auto-detect: Kernel image requires new device naming scheme.
emulator: Auto-detect: Kernel does not support YAFFS2 partitions.
emulator: autoconfig: -ramdisk /Volumes/MacOs_disk/AOSP/android-6.0.0_r6.tmp/build_out/target/product/generic/ramdisk.img
emulator: autoconfig: -sysdir /Volumes/MacOs_disk/AOSP/android-6.0.0_r6.tmp/build_out/target/product/generic
emulator: Using initial system image: /Volumes/MacOs_disk/AOSP/android-6.0.0_r6.tmp/build_out/target/product/generic/system.img
emulator: WARNING: system partition size adjusted to match image file (1536 MB > 200 MB)

emulator: autoconfig: -data /Volumes/MacOs_disk/AOSP/android-6.0.0_r6.tmp/build_out/target/product/generic/userdata-qemu.img
emulator: autoconfig: -initdata /Volumes/MacOs_disk/AOSP/android-6.0.0_r6.tmp/build_out/target/product/generic/userdata.img
emulator: WARNING: data partition size adjusted to match image file (550 MB > 200 MB)

emulator: autoconfig: -cache /Volumes/MacOs_disk/AOSP/android-6.0.0_r6.tmp/build_out/target/product/generic/cache.img
emulator: Physical RAM size: 512MB

emulator: GPU emulation is disabled
emulator: WARNING: CPU acceleration only works with x86/x86_64 system images.
emulator: Target arch = 'arm64'
Content of hardware configuration file:
hw.cpu.arch = arm
hw.ramSize = 512
hw.screen = touch
hw.mainKeys = yes
hw.trackBall = yes
hw.keyboard = no
hw.keyboard.lid = no
hw.keyboard.charmap = qwerty2
hw.dPad = yes
hw.gsmModem = yes
hw.gps = yes
hw.battery = yes
hw.accelerometer = yes
hw.audioInput = yes
hw.audioOutput = yes
hw.sdCard = yes
disk.cachePartition = yes
disk.cachePartition.path = /Volumes/MacOs_disk/AOSP/android-6.0.0_r6.tmp/build_out/target/product/generic/cache.img
disk.cachePartition.size = 66m
hw.lcd.width = 320
hw.lcd.height = 480
hw.lcd.depth = 16
hw.lcd.density = 160
hw.lcd.backlight = yes
hw.gpu.enabled = no
hw.initialOrientation = portrait
hw.camera.back = emulated
hw.camera.frOnt= none
vm.heapSize = 48
hw.sensors.proximity = yes
hw.sensors.magnetic_field = yes
hw.sensors.orientation = yes
hw.sensors.temperature = yes
hw.useext4 = yes
kernel.path = /Volumes/MacOs_disk/AOSP/android-6.0.0_r6/prebuilts/qemu-kernel/arm64/kernel-qemu
kernel.parameters = androidboot.hardware=goldfish android.checkjni=1
kernel.newDeviceNaming = yes
kernel.supportsYaffs2 = no
disk.ramdisk.path = /Volumes/MacOs_disk/AOSP/android-6.0.0_r6.tmp/build_out/target/product/generic/ramdisk.img
disk.systemPartition.initPath = /Volumes/MacOs_disk/AOSP/android-6.0.0_r6.tmp/build_out/target/product/generic/system.img
disk.systemPartition.size = 1536m
disk.dataPartition.path = /Volumes/MacOs_disk/AOSP/android-6.0.0_r6.tmp/build_out/target/product/generic/userdata-qemu.img
disk.dataPartition.size = 550m
avd.name = <build>
.
QEMU options list:
emulator: argv[00] = "/Volumes/MacOs_disk/AOSP/android-6.0.0_r6/prebuilts/android-emulator/darwin-x86_64/emulator64-arm"
emulator: argv[01] = "-android-hw"
emulator: argv[02] = "/Volumes/MacOs_disk/AOSP/android-6.0.0_r6.tmp/build_out/target/product/generic/hardware-qemu.ini"
Concatenated QEMU options:
/Volumes/MacOs_disk/AOSP/android-6.0.0_r6/prebuilts/android-emulator/darwin-x86_64/emulator64-arm -android-hw /Volumes/MacOs_disk/AOSP/android-6.0.0_r6.tmp/build_out/target/product/generic/hardware-qemu.ini
emulator: registered 'boot-properties' qemud service
emulator: Using kernel serial device prefix: ttyGF
emulator: Ramdisk image contains fstab.goldfish file
emulator: Found format of system partition: 'ext4'
emulator: Found format of userdata partition: 'ext4'
emulator: Found format of cache partition: 'ext4'
emulator: system partition format: ext4
emulator: Mapping 'system' partition image to /tmp/android-tom/emulator-wUTFrp
emulator: nand_add_dev: system,size=0x60000000,file=/tmp/android-tom/emulator-wUTFrp,initfile=/Volumes/MacOs_disk/AOSP/android-6.0.0_r6.tmp/build_out/target/product/generic/system.img,pagesize=512,extrasize=0
emulator: userdata partition format: ext4
emulator: nand_add_dev: userdata,size=0x22600000,file=/Volumes/MacOs_disk/AOSP/android-6.0.0_r6.tmp/build_out/target/prodct/generic/userdata-qemu.img,pagesize=512,extrasize=0
emulator: cache partition format: ext4
emulator: nand_add_dev: cache,size=0x4200000,file=/Volumes/MacOs_disk/AOSP/android-6.0.0_r6.tmp/build_out/target/product/generic/cache.img,pagesize=512,extrasize=0
emulator: registered 'boot-properties' qemud service
emulator: Adding boot property: 'dalvik.vm.heapsize' = '48m'
emulator: Adding boot property: 'ro.config.low_ram' = 'true'
emulator: Adding boot property: 'qemu.sf.lcd_density' = '160'
emulator: Adding boot property: 'qemu.hw.mainkeys' = '1'
emulator: Adding boot property: 'qemu.sf.fake_camera' = 'back'
emulator: Kernel parameters: qemu.gles=0 qemu=1 cOnsole=ttyGF0 android.qemud=ttyGF1 androidboot.hardware=goldfish android.checkjni=1 ndns=1
emulator: autoconfig: -scale 1
emulator: Forcing ro.adb.qemud to "0".
emulator: control console listening on port 5554, ADB on port 5555
emulator: can't connect to ADB server: Socket is not connected (errno = 57)
emulator: setting up http proxy: server=127.0.0.1 port=8889
emulator: android_hw_fingerprint_init: fingerprint qemud listen service initialized

emulator: ping program: /Volumes/MacOs_disk/AOSP/android-6.0.0_r6/prebuilts/android-emulator/darwin-x86_64/ddms

@dankai
是说 `lunch sdk_phone_armv8a-userdebug` 吗
我创建了一个 arm64-v8a 的模拟器 , 设备信息中的 builder number 是 sdk_phone_arm64-userdebug
所以说我改用 `lunch sdk_phone_arm64-userdebug` 是吧