derpfest-aosp / manifest

DerpFest

Getting Started

To get started with Android, you'll need to get familiar with Source Control Tools. To set up your build environment and sync DerpFest, please follow this guide: Link

To initialize your local repository using the AOSP/CAF based DerpFest source, use a command like this:

repo init -u https://github.com/DerpFest-AOSP/manifest.git -b 14

Sync up with this command:

repo sync -c --force-sync --optimized-fetch --no-tags --no-clone-bundle --prune -j$(nproc --all)

Building the source

The source at DerpFest is well configured for building.

Initiate the build with:

. build/envsetup.sh

Prepare your device with:

lunch derp_$device-user

Then fire it off with:

mka derp

Thanks section

Here's my thanks to people who made this possible:

• ABC
• AICP
• AOSiP
• AOSPA
• ArrowOS
• Bianca Project
• BootleggersROM
• CyanogenMod/LineageOS
• DirtyUnicorns
• NitrogenOS
• Nusantara-ROM
• OmniROM
• PixelExperience
• POSP
• Project Fluid
• Project Kaleidoscope
• RiceDroid
• ShapeShiftOS
• Syberia Project
• YAAP

Using our assets

Code

Our codebase is licensed under Apache License, Version 2.0 unless otherwise specified. Apache License 2.0 allows a variety of actions on the content as long as licensing and copyright notices are retained and included with the code and your changes to the codebase are stated.

You can read the full license text at http://www.apache.org/licenses/LICENSE-2.0

Images & other assets

Unless otherwise specified, all out assets, including but not limited to images, are licensed under Creative Commons Attribution-NonCommercial 4.0 International, or CC BY-NC 4.0 for short. This means that you are allowed to modify the aforementioned assets in any way you want and you are free to share the originals and/or the modified work. However, you are not allowed to use the assets for commercial purposes and you must provide attribution at all times which means you have to include a short note about the license used (CC BY-NC 4.0), the original author/authors (DerpFest) and inform about any changes that have been made. A link to the website ( derpfest.org ) should usually be included as well.

You can reach the full legal text at http://creativecommons.org/licenses/by-nc/4.0/

manifest's Issues

Problem building

After syncing repo and lunching "derp_dumpling-userdebug" I go to "mka derp" and get this problem https://del.dog/raw/linexexely

Building Issue

i keep getting this error for some reason

"/bin/sh: out/../device/motorola/def/dtc/dtc: No such file or directory"

Device tree for toco

Where can i find device tree for mi note 10 lite (toco) ? Can't find it anywhere

WebUSB-based installer

The command-line approach offers a way to install DerpFest OS without trusting our server infrastructure. This requires being on an OS with proper fastboot and signify packages along with understanding the process enough to avoid blindly trusting the instructions from our site. For most users, the web-based installation approach is no less secure and avoids needing any software beyond a browser with WebUSB support.

Officially supported browsers for the web install method:

• Chromium (outside Ubuntu, since they ship a broken Snap package without working WebUSB)
• Google Chrome
• Microsoft Edge
• Brave (with Brave Shields disabled, since it caps storage usage at a low value to avoid fingerprinting available storage)
  You should avoid Flatpak and Snap versions of browsers, as they're known to cause issues during the installation process.

Make sure your browser is up-to-date before proceeding.

Do not use Incognito or other private browsing modes. These modes usually prevent the web installer from having enough storage space to extract the downloaded release.

Issue when syncing rom manifest

Linus Guglielmo, [30.10.21 17:29]
Checking out: 63% (544/863) AOSiP/platform_prebuilts_clang_host_linux-x86error: Cannot checkout vendor_gms: ManifestInvalidRevisionError: revision 11 in vendor_gms not found
Checking out: 63% (544/863), done in 47m38.309s
error: in sync -j10 --force-sync: revision 11 in vendor_gms not found

Is there a way to solve this error?

why

hardware/qcom-caf/sm8150/display/sdm/libs/core/drm/hw_device_drm.cpp:599:22: error: use of undeclared identifier 'DRM_MODE_FLAG_CMD_MODE_PANEL'
if (mode.flags & DRM_MODE_FLAG_CMD_MODE_PANEL) {
^
hardware/qcom-caf/sm8150/display/sdm/libs/core/drm/hw_device_drm.cpp:734:28: error: use of undeclared identifier 'DRM_MODE_FLAG_CMD_MODE_PANEL'
if (current_mode.flags & DRM_MODE_FLAG_CMD_MODE_PANEL) {
^
hardware/qcom-caf/sm8150/display/sdm/libs/core/drm/hw_device_drm.cpp:737:28: error: use of undeclared identifier 'DRM_MODE_FLAG_VID_MODE_PANEL'
if (current_mode.flags & DRM_MODE_FLAG_VID_MODE_PANEL) {
^
hardware/qcom-caf/sm8150/display/sdm/libs/core/drm/hw_device_drm.cpp:853:22: error: use of undeclared identifier 'DRM_MODE_FLAG_CMD_MODE_PANEL'
if (to_set.flags & DRM_MODE_FLAG_CMD_MODE_PANEL) {
^
hardware/qcom-caf/sm8150/display/sdm/libs/core/drm/hw_device_drm.cpp:854:17: error: use of undeclared identifier 'DRM_MODE_FLAG_CMD_MODE_PANEL'
mode_flag = DRM_MODE_FLAG_CMD_MODE_PANEL;
^
hardware/qcom-caf/sm8150/display/sdm/libs/core/drm/hw_device_drm.cpp:855:24: error: use of undeclared identifier 'DRM_MODE_FLAG_VID_MODE_PANEL'
switch_mode_flag = DRM_MODE_FLAG_VID_MODE_PANEL;
^
hardware/qcom-caf/sm8150/display/sdm/libs/core/drm/hw_device_drm.cpp:856:29: error: use of undeclared identifier 'DRM_MODE_FLAG_VID_MODE_PANEL'
} else if (to_set.flags & DRM_MODE_FLAG_VID_MODE_PANEL) {
^
hardware/qcom-caf/sm8150/display/sdm/libs/core/drm/hw_device_drm.cpp:857:17: error: use of undeclared identifier 'DRM_MODE_FLAG_VID_MODE_PANEL'
mode_flag = DRM_MODE_FLAG_VID_MODE_PANEL;
^
hardware/qcom-caf/sm8150/display/sdm/libs/core/drm/hw_device_drm.cpp:858:24: error: use of undeclared identifier 'DRM_MODE_FLAG_CMD_MODE_PANEL'
switch_mode_flag = DRM_MODE_FLAG_CMD_MODE_PANEL;
^
hardware/qcom-caf/sm8150/display/sdm/libs/core/drm/hw_device_drm.cpp:861:28: error: use of undeclared identifier 'DRM_MODE_FLAG_CMD_MODE_PANEL'
if (current_mode.flags & DRM_MODE_FLAG_CMD_MODE_PANEL) {
^
hardware/qcom-caf/sm8150/display/sdm/libs/core/drm/hw_device_drm.cpp:862:22: error: use of undeclared identifier 'DRM_MODE_FLAG_CMD_MODE_PANEL'
curr_mode_flag = DRM_MODE_FLAG_CMD_MODE_PANEL;
^
hardware/qcom-caf/sm8150/display/sdm/libs/core/drm/hw_device_drm.cpp:863:35: error: use of undeclared identifier 'DRM_MODE_FLAG_VID_MODE_PANEL'
} else if (current_mode.flags & DRM_MODE_FLAG_VID_MODE_PANEL) {
^
hardware/qcom-caf/sm8150/display/sdm/libs/core/drm/hw_device_drm.cpp:864:22: error: use of undeclared identifier 'DRM_MODE_FLAG_VID_MODE_PANEL'
curr_mode_flag = DRM_MODE_FLAG_VID_MODE_PANEL;
^
hardware/qcom-caf/sm8150/display/sdm/libs/core/drm/hw_device_drm.cpp:915:21: error: use of undeclared identifier 'DRM_MODE_FLAG_VID_MODE_PANEL'
if (mode_flag & DRM_MODE_FLAG_VID_MODE_PANEL) {
^
hardware/qcom-caf/sm8150/display/sdm/libs/core/drm/hw_device_drm.cpp:945:52: error: use of undeclared identifier 'DRM_MODE_FLAG_VID_MODE_PANEL'
(connector_info_.modes[index].mode.flags & DRM_MODE_FLAG_VID_MODE_PANEL) ?
^
hardware/qcom-caf/sm8150/display/sdm/libs/core/drm/hw_device_drm.cpp:1282:29: error: use of undeclared identifier 'DRM_MODE_FLAG_VID_MODE_PANEL'
if (panel_mode_changed_ & DRM_MODE_FLAG_VID_MODE_PANEL) {
^
hardware/qcom-caf/sm8150/display/sdm/libs/core/drm/hw_device_drm.cpp:1564:30: error: use of undeclared identifier 'DRM_MODE_FLAG_CMD_MODE_PANEL'
if (panel_mode_changed_ & DRM_MODE_FLAG_CMD_MODE_PANEL) {
^
hardware/qcom-caf/sm8150/display/sdm/libs/core/drm/hw_device_drm.cpp:1567:36: error: use of undeclared identifier 'DRM_MODE_FLAG_VID_MODE_PANEL'
} else if (panel_mode_changed_ & DRM_MODE_FLAG_VID_MODE_PANEL) {
^
hardware/qcom-caf/sm8150/display/sdm/libs/core/drm/hw_device_drm.cpp:1786:17: error: use of undeclared identifier 'DRM_MODE_FLAG_CMD_MODE_PANEL'
mode_flag = DRM_MODE_FLAG_CMD_MODE_PANEL;
^
fatal error: too many errors emitted, stopping now [-ferror-limit=]

Building issue

Alright, so I re-synced the repo and the initial exfat problem seems to be solved, however, I still get this error: https://del.dog/raw/uttowoofur