קל לארגן דפים בעזרת אוספים
אפשר לשמור ולסווג תוכן על סמך ההעדפות שלך.
המדריך הזה מיועד בעיקר למפתחים שרוצים לבדוק ולפתח באמצעות AAOS
נקודות שצריך לשים לב אליהן:
המגבלות האלה חלות כשמשתמשים ב-Pixel כפלטפורמות פיתוח:
מכשיר Pixel Tablet מאומת ונתמך. אפשר לרכוש אותו ב-Google Store.
יש תמיכה במכשירים הבאים, אבל הם לא נבדקים באופן פעיל. חשוב להוריד את הקבצים הבינאריים הנכונים, ולאחר מכן לפעול לפי ההוראות ולשנות את הפקודות לפי הצורך:
דוגמאות התוכן והקוד שבדף הזה כפופות לרישיונות המפורטים בקטע רישיון לתוכן. Java ו-OpenJDK הם סימנים מסחריים או סימנים מסחריים רשומים של חברת Oracle ו/או של השותפים העצמאיים שלה.
עדכון אחרון: 2025-07-27 (שעון UTC).
[[["התוכן קל להבנה","easyToUnderstand","thumb-up"],["התוכן עזר לי לפתור בעיה","solvedMyProblem","thumb-up"],["סיבה אחרת","otherUp","thumb-up"]],[["חסרים לי מידע או פרטים","missingTheInformationINeed","thumb-down"],["התוכן מורכב מדי או עם יותר מדי שלבים","tooComplicatedTooManySteps","thumb-down"],["התוכן לא עדכני","outOfDate","thumb-down"],["בעיה בתרגום","translationIssue","thumb-down"],["בעיה בדוגמאות/בקוד","samplesCodeIssue","thumb-down"],["סיבה אחרת","otherDown","thumb-down"]],["עדכון אחרון: 2025-07-27 (שעון UTC)."],[],[],null,["# Pixel devices as development platforms\n\nThis guide is mainly for developers who want to test and develop using AAOS\n\nCaveats\n-------\n\nThese limitations apply when using a Pixel as development platforms:\n| **Caution:** There is a chance that you can brick your device when using Pixel as a development platform. If a device become bricked, have it repaired by [Google Support.](https://store.google.com/magazine/support)\n\n- The Pixel Tablet is verified and supported. You can visit\n [Google Store](https://store.google.com/product/pixel_tablet) to purchase it.\n\n- The following devices are supported but not actively tested. Be sure to download the correct binaries and then follow the instructions and change the commands as required:\n - Pixel 7, 7a and 7Pro\n - Pixel 8 and 8Pro\n- You *must* use Android 14 , build\n [android-14.0.0_r30](/setup/start/build-numbers#source-code-tags-and-builds).\n\n- Limited support for Bluetooth profiles and some of the profiles will not work at all\n- Tablet does not support GPS, location requires \"mock location app or similar\"\n\nPrerequisites\n-------------\n\nBefore you continue, confirm you have the following items:\n\n1. **OEM unlocking is required.**\n2. **Linux desktop capable of building Android code.** For more information, see [Establishing a Build Environment](/setup/build/initializing).\n\nCode sync and build\n-------------------\n\n1. To sync Android build AP1A.240405.002 : \n\n ```scdoc\n mkdir aaos_on_pixel\n cd aaos_on_pixel\n REPO_ALLOW_SHALLOW=0 repo init -c -u https://android.googlesource.com/platform/manifest -b android-14.0.0_r30 --use-superproject --partial-clone --partial-clone-exclude=platform/frameworks/base --clone-filter=blob:limit=10M \n repo sync -j32\n ```\n2. Download the vendor image for pixel devices from [developers.google.com](https://developers.google.com/android/drivers) for AP1A.240405.002 \n\n ```scdoc\n curl --output - https://dl.google.com/dl/android/aosp/google_devices-tangorpro-ap1a.240405.002-8d141153.tgz | tar -xzvf -\n tail -n +315 extract-google_devices-tangorpro.sh | tar -zxvf -\n ```\n3. Take a patch \n\n ```carbon\n cd packages/services/Car\n git fetch https://android.googlesource.com/platform/packages/services/Car refs/changes/83/3037383/2 && git cherry-pick FETCH_HEAD #fix the audio crash\n cd -\n ```\n4. Run the build. : \n\n ```scdoc\n . build/envsetup.sh\n lunch aosp_tangorpro_car-ap1a-userdebug\n m\n ```\n5. Build the Automotive-related packages: \n\n ```objective-c\n m android.hardware.automotive.vehicle@2.0-default-service android.hardware.automotive.audiocontrol-service.example \n ```\n\nSet up the device to flash the build\n------------------------------------\n\nIf you haven't already done so, enable **Developer options**. Go to Settings \\\u003e\nSystem \\\u003e About Phone and then tap Build Number seven times.\n\nWhen you've enabled Developer options:\n\n1. Go to Settings \\\u003e System \\\u003e Developer options and enable **USB debugging** and **OEM unlocking**:\n\n|---|---|\n| | |\n\nFlash the build\n---------------\n\n1. To place the device into fastboot mode and then unlock it: \n\n ```gdscript\n adb reboot bootloader\n fastboot flashing unlock\n ```\n2. On the device, select Unlock the Bootloader. Doing so erases ***all*** data on the device!\n3. To flash the build: \n\n ```text\n fastboot -w flashall\n ```\n4. After the build start booting with animation:\n 1. To enable `adb remount`: \n\n ```text\n #Temporary disable the userdata checkpoint \n adb wait-for-device root; sleep 3; adb shell vdc checkpoint commitChanges; sleep 2 \n #Enable remount\n adb remount && sleep 2 && adb reboot && echo \"rebooting the device\" && adb wait-for-device root && sleep 5 && adb remount\n ```\n 2. To push the required Automotive-specific files to the device: \n\n ```text\n adb sync vendor && adb reboot\n ```\n 3. Wait for the device to start: \n\n Tips\n ----\n\n5. If you see screen brightness too low: \n\n ```scdoc\n adb shell settings put system screen_brightness 255\n ```\n6. Boot when charger is plugged in: \n\n ```gdscript\n adb reboot bootloader \n fastboot oem off-mode-charge 1\n fastboot reboot\n ```\n7. Enable Mock location: \n\n ```scdoc\n adb unroot\n adb shell cmd location set-location-enabled true\n adb root\n adb shell appops set 0 android:mock_location allow\n adb shell cmd location providers add-test-provider gps\n adb shell cmd location providers set-test-provider-enabled gps true\n adb shell cmd location providers set-test-provider-location gps --location 37.090200,-95.712900\n #To verify\n adb shell dumpsys location | grep \"last location\"\n ```"]]
