I'm trying to eliminate all **Google** and **Meta** services from my digital life. (I don't like their policies.) So I thought about buying a new smartphone, removing the pre-installed ROM, and installing Android AOSP without Google **Gapps**. However, the question I would like to ask is whether programmatically, a lot of information from my AOSP smartphone will communicate some information with Google despite not using their services. Is removing Gapps enough, or could something else be done? Is there empirical evidence in the code that confirms this? Considering that for web browsing I would mainly use Mozilla Firefox with DuckDuckGo thus avoiding any Chromium-based browser, and for messaging Telegram downloaded from their Website. (I haven't used WhatsApp for several years.)

I want to have a adbd in debug mode on my Pixel 6a. The easiest way to get it would be to flash a userdebug image as suggested by [f.e. official guides](https://source.android.com/docs/setup/create/new-device#build-variants) . Using the flash.android.com tool does not work because it does not include userdebug builds (anymore?). Is there any place where one can find pre-built userdebug builds? Is there any other way except for building a full AOSP image myself?

I'm creating a device tree for the Motorola Moto G50. The device uses DWC3 USB controller. In AOSP recovery, ADB over USB works, and adb (device? gadget?) is mounted correctly: # mount adb on /dev/usb-ffs/adb type functionfs (rw,relatime) This mount is done by the Android init system in the on fs trigger: on fs mkdir /dev/usb-ffs 0775 shell shell mkdir /dev/usb-ffs/adb 0770 shell shell mount functionfs adb /dev/usb-ffs/adb uid=2000,gid=2000 However, similar init commands (taken from the device's stock init scripts) when booting into the system: mkdir /dev/usb-ffs 0775 shell system mkdir /dev/usb-ffs/adb 0770 shell system mount functionfs adb /dev/usb-ffs/adb uid=2000,gid=1000,rmode=0770,fmode=0660 results in this error: [ 36.024282] init: Command 'mount functionfs adb /dev/usb-ffs/adb uid=2000,gid=1000,rmode=0770,fmode=0660' action=boot (/vendor/etc/init/hw/init.qcom.rc:34) took 0ms and failed: mount() failed: No such device

I am a complete newbie to AOSP and I'm having trouble building and flashing android kernel for Pixel 8. I've been trying to follow [Building Pixel Kernels](https://source.android.com/docs/setup/build/building-pixel-kernels) instructions, but I'm experiencing some issues. I think my problem is that **I don't know which platform manifest branch to use with which kernel manifest branch.** - When I try to [flash the device using flash.android.com](https://source.android.com/docs/setup/build/building-pixel-kernels#flash_the_device_using_flashandroidcom) , there are no instructions on which platform and kernel combination is supported for Pixel 8 device (there's [a table](https://source.android.com/docs/setup/build/building-pixel-kernels#supported-kernel-branches) but it only has information regarding Pixel 6). I tried flashing git-aosp-main-with-phones, but after flashing the kernel, Pixel 8 will not boot correctly. I built the kernel by repo init & sync -ing android-gs-shusky-5.15-android14-d1 branch from android kernel manifest. I followed [the guide](https://source.android.com/docs/setup/build/building-pixel-kernels#download_and_compile_the_kernel) from the same instructions mentioned above for fetching kernel source, building it, and flashing it. But the device only displays android logo and after a few minutes, kernel panics. - I decided to try fetching and building the platform myself, and I tried following combinations: - platform manifest android-14.0.0_r27 and kernel manifest android-gs-shusky-5.15-android14-d1 - results: kernel panics after a couple of minutes - platform manifest android-14.0.0_r6 and kernel manifest android-gs-shusky-5.15-android14-qpr1 - results: kernel doesn't panic, but Pixel 8 displays Google logo and doesn't proceed If someone could point me to a working platform and kernel combination for Pixel 8, (or if I'm doing something else wrong) it would be extremely helpful!

Was wondering how to install an ‘apk’ on a TCL Flip Go (AOSP version 11) phone? I already tried to turn on USB debugging mode in order to install an apk with adb. But unable to follow the instructions for enabling USB debugging for a TCL Flip phone (here: https://www.tcl.com/global/en/support-mobile/faq/7541) because there is not a Build number field and entry in the About Phone section. As well, tried to follow the instructions here: https://github.com/neutronscott/flip2/wiki . But when running python3 mtk-bootseq.py FASTBOOT /dev/ttyACM0 (used ttyACM0 as that is what would pop up for the flip phone when running dmesg -w) upon the phone booting it would be able to send serial messages for a second or so then not be able to send.

Hello I have an old Samsung Galaxy A51 (SM-A515F/DSN) running on Android 13. I want to turn it into a small server, so to do so, I need to install "Linux deploy" (it needs root), but for debloating and efficiency reasons, I want to install a pure Android version, as I need no Google service. The operating system will just be the host for "Linux deploy". I know this may seem out of the scope of my question and may be the topic for the next thread but I'm just giving background information. The main question is "How to flash vanilla AOSP and root my Samsung A51 device?"

I see [stackoverflow.com/revisions/20060853/1](https://stackoverflow.com/revisions/20060853/1) (paraphrased unmdermentioned), which appears to answer a similar question, although the answer that it provides causes me to believe that the services are *hardcoded* inside a user-inaccessible (even with standard adb access) POSIX Shell Script:

The statement "Service declarations only serve to describe services, they do not actually start anything" is correct. The native daemons are actually started in init.rc by lines 371-372 in [android.googlesource.com/platform/system/core/+/master/rootdir/init.rc](https://android.googlesource.com/platform/system/core/+/master/rootdir/init.rc) : - class_start core - class_start main ...where all daemons that belong to class *core* and class *main* are started respectively.

[Another answer, from *this* forum](https://android.stackexchange.com/revisions/6559/1#:~:text=/data/init.sh%20runs%20at%20boot%2C%20if%20you%20have%20root%20you%20can%20edit%20it%20as%20you%20like.) , to a similar question, mentions a near-duplicate file that acts identically (although it doesn't elaborate much – it, too, is paraphrased undermentioned): > /data/init.sh runs at boot. If you have root, you can edit it as you like. Inherently, their formats don't render them application-unmodifiable, but the sole alternative example of a user-modifiable shell script configuration file that I've seen is GRUB2's /etc/default/grub, which I was under the impression was a *singularly* exceptional circumstance, especially because modifying it necessitates superuser permissions. Relevantly, the security reduction that would arise from permitting applications to add arbitrary shell commands to that script would be obvious enough that I do not envisage this being the method by which services are added and configured. Consequently, does AOSP include an initialisation system that applications can add to? ##### Rationale The reason I ask here is because I'm asking as a user instead of a developer. That may appear nonsensical, but hopefully situations like [github.com/TacoTheDank/Scoop/issues/65#issuecomment-2571309312](https://github.com/TacoTheDank/Scoop/issues/65#issuecomment-2571309312) , in which users must utilize development tools to bypass platform restrictions, provide adequate rationale.

**Rationale** I have approximately 15 devices with AOSP distributions installed. These are mostly OEM derivatives, with Google Mobile Services (GMS), installed onto bare metal (via the bootloader's recovery). I also have some BlissOS installations, operable via WayDroid (installed on Fedora 41, postmarketOS, and openSUSE Tumbleweed, although this shouldn't matter). Initialising all of these devices can be tiresome. Additionally, sometimes I want to compare hardware capabilities, like boot time. This means that I want them to commence OS initialisation simultaneously. Consequently, I want to know whether these devices’ and hypervisor(-abstracted)s’ installations can be initialised via a WOL (wake-on-LAN) packet. **Potential Solutions** I've located [chromium.googlesource.com/aosp/platform/system/connectivity/shill/+/57a957e8112a42ce0cf16fbe94f6a482b937db42/bin/set_wake_on_lan](https://chromium.googlesource.com/aosp/platform/system/connectivity/shill/+/57a957e8112a42ce0cf16fbe94f6a482b937db42/bin/set_wake_on_lan) , but I don't know whether this is what I'm looking for, because I'm no POSIX shell script savant. [reddit.com/r/AndroidTV/comments/zcpqf6/comment/iyycefy](https://www.reddit.com/r/AndroidTV/comments/zcpqf6/comment/iyycefy/) appears to indicate that this is included by some Android TV OEMs.

My Android device is an AOSP 14 launch device, based on x86_64 architecture, bootloader is also unlocked. **Seamless A/B** support and **Dynamic partitions** support is present in my device. Also I can switch slots using **fastbootd** (fastboot set_active ). By flashing images to both slots, I can set _a/_b slot as active and the device will boot with that slot. Recently, I enabled virtual A/B support in the device. Is slot switching still possible with **fastbootd**? As far as I know, with virtual A/B, slot_a and slot_b dynamic partitions will **not** present inside the super image at a time, slot switch will happen only through OTA. During OTA, the update will get snapshotted and applied on the base device, and if it succeeded, that snapshot got merged with the base device and the active slot will be switched to another slot.

**Background:** Please check following links 1. How to disable dm-verity on Android with “user” build type ROM? 2. Stuck in boot-loop when unpack and pack system.img? **Update:** So, I am trying to disable dm-verity on my Samsung S10 5G device to successfully flash an unpack, unmodified and then packed system.img.ext4.lz4 file(with another ROM files) using Odin. I have tried the following things: 1. Removed avb flag from boot.img with following commands:

# magiskboot dtb boot.img print -f
> #345900: fstab
│  [compatible]: [android,fstab]
├── #345940: vendor
│      [compatible]: [android,vendor]
│      [dev]: [/dev/block/platform/soc/8804000.sdhci/by-name/vendor]
│      [type]: [ext4]
│      [mnt_flags]: [ro,barrier=1,discard]
│      [fsmgr_flags]: [wait,slotselect,avb]
│      [status]: [ok]
└── #346156: vm-linux






#343692: fstab
│  [compatible]: [android,fstab]
├── #343732: vendor
│      [compatible]: [android,vendor]
│      [dev]: [/dev/block/platform/soc/8804000.sdhci/by-name/vendor]
│      [type]: [ext4]
│      [mnt_flags]: [ro,barrier=1,discard]
│      [fsmgr_flags]: [wait,slotselect,avb]
│      [status]: [ok]
└── #343948: vm-linux








# magiskboot dtb boot.img patch

# magiskboot dtb boot.img print -f
> #345900: fstab
│  [compatible]: [android,fstab]
├── #345940: vendor
│      [compatible]: [android,vendor]
│      [dev]: [/dev/block/platform/soc/8804000.sdhci/by-name/vendor]
│      [type]: [ext4]
│      [mnt_flags]: [ro,barrier=1,discard]
│      [fsmgr_flags]: [wait,slotselect]
│      [status]: [ok]
└── #346152: vm-linux






#343692: fstab
│  [compatible]: [android,fstab]
├── #343732: vendor
│      [compatible]: [android,vendor]
│      [dev]: [/dev/block/platform/soc/8804000.sdhci/by-name/vendor]
│      [type]: [ext4]
│      [mnt_flags]: [ro,barrier=1,discard]
│      [fsmgr_flags]: [wait,slotselect]
│      [status]: [ok]
└── #343944: vm-linux

2. Removed avb and verify flags from dtbo.img with following commands:

# magiskboot dtb dtbo.img print -f
> #126600: fstab
├── #126612: product
│      [compatible]: [android,product]
│      [dev]: [/dev/block/platform/soc/1d84000.ufshc/by-name/product]
│      [type]: [ext4]
│      [mnt_flags]: [ro,errors=panic]
│      [fsmgr_flags]: [wait,verify,avb]
└── #126800: vendor





#126596: fstab
├── #126608: product
│      [compatible]: [android,product]
│      [dev]: [/dev/block/platform/soc/1d84000.ufshc/by-name/product]
│      [type]: [ext4]# magiskboot dtb dtbo.img print -f
│      [mnt_flags]: [ro,errors=panic]
│      [fsmgr_flags]: [wait,verify,avb]
└── #126796: vendor





#126600: fstab
├── #126612: product
│      [compatible]: [android,product]
│      [dev]: [/dev/block/platform/soc/1d84000.ufshc/by-name/product]
│      [type]: [ext4]
│      [mnt_flags]: [ro,errors=panic]
│      [fsmgr_flags]: [wait,verify,avb]
└── #126800: vendor





#126600: fstab
├── #126612: product
│      [compatible]: [android,product]
│      [dev]: [/dev/block/platform/soc/1d84000.ufshc/by-name/product]
│      [type]: [ext4]
│      [mnt_flags]: [ro,errors=panic]
│      [fsmgr_flags]: [wait,verify,avb]
└── #126800: vendor





#126600: fstab
├── #126612: product
│      [compatible]: [android,product]
│      [dev]: [/dev/block/platform/soc/1d84000.ufshc/by-name/product]
│      [type]: [ext4]
│      [mnt_flags]: [ro,errors=panic]
│      [fsmgr_flags]: [wait,verify,avb]
└── #126800: vendor





#126600: fstab
├── #126612: product
│      [compatible]: [android,product]
│      [dev]: [/dev/block/platform/soc/1d84000.ufshc/by-name/product]
│      [type]: [ext4]
│      [mnt_flags]: [ro,errors=panic]
│      [fsmgr_flags]: [wait,verify,avb]
└── #126800: vendor







# magiskboot dtb dtbo.img patch


# magiskboot dtb dtbo.img print -f
> #126600: fstab
├── #126612: product
│      [compatible]: [android,product]
│      [dev]: [/dev/block/platform/soc/1d84000.ufshc/by-name/product]
│      [type]: [ext4]
│      [mnt_flags]: [ro,errors=panic]
│      [fsmgr_flags]: [wait,]
└── #126792: vendor





#126596: fstab
├── #126608: product
│      [compatible]: [android,product]
│      [dev]: [/dev/block/platform/soc/1d84000.ufshc/by-name/product]
│      [type]: [ext4]
│      [mnt_flags]: [ro,errors=panic]
│      [fsmgr_flags]: [wait,]
└── #126788: vendor





#126600: fstab
├── #126612: product
│      [compatible]: [android,product]
│      [dev]: [/dev/block/platform/soc/1d84000.ufshc/by-name/product]
│      [type]: [ext4]
│      [mnt_flags]: [ro,errors=panic]
│      [fsmgr_flags]: [wait,]
└── #126792: vendor





#126600: fstab
├── #126612: product
│      [compatible]: [android,product]
│      [dev]: [/dev/block/platform/soc/1d84000.ufshc/by-name/product]
│      [type]: [ext4]
│      [mnt_flags]: [ro,errors=panic]
│      [fsmgr_flags]: [wait,]
└── #126792: vendor





#126600: fstab
├── #126612: product
│      [compatible]: [android,product]
│      [dev]: [/dev/block/platform/soc/1d84000.ufshc/by-name/product]
│      [type]: [ext4]
│      [mnt_flags]: [ro,errors=panic]
│      [fsmgr_flags]: [wait,]
└── #126792: vendor





#126600: fstab
├── #126612: product
│      [compatible]: [android,product]
│      [dev]: [/dev/block/platform/soc/1d84000.ufshc/by-name/product]
│      [type]: [ext4]
│      [mnt_flags]: [ro,errors=panic]
│      [fsmgr_flags]: [wait,]
└── #126792: vendor

3. Patched ramdisk.cpio with following commands:

# magiskboot cpio ./initrd 'patch false true'
Loading cpio: [./initrd]
Patch with flag KEEPVERITY=[false] KEEPFORCEENCRYPT=[false]
Found fstab file [etc/recovery.fstab]
Dump cpio: [./initrd]

# magiskboot cpio ./initrd extract
# cat etc/recovery.fstab
> # Copyright (c) 2013, The Linux Foundation. All rights reserved.
#
# Redistribution and use in source and binary forms, with or without
# modification, are permitted provided that the following conditions are
# met:
#     * Redistributions of source code must retain the above copyright
#       notice, this list of conditions and the following disclaimer.
#     * Redistributions in binary form must reproduce the above
#       copyright notice, this list of conditions and the following
#       disclaimer in the documentation and/or other materials provided
#       with the distribution.
#     * Neither the name of The Linux Foundation nor the names of its
#       contributors may be used to endorse or promote products derived
#       from this software without specific prior written permission.
#
# THIS SOFTWARE IS PROVIDED "AS IS" AND ANY EXPRESS OR IMPLIED
# WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF
# MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NON-INFRINGEMENT
# ARE DISCLAIMED.  IN NO EVENT SHALL THE COPYRIGHT OWNER OR CONTRIBUTORS
# BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR
# CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF
# SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR
# BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY,
# WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE
# OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN
# IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.

#                                                
/dev/block/bootdevice/by-name/boot        /boot           emmc        defaults                  recoveryonly
/dev/block/bootdevice/by-name/recovery    /recovery       emmc        defaults                  recoveryonly
/dev/block/bootdevice/by-name/system      /               ext4        defaults                  recoveryonly
/dev/block/bootdevice/by-name/userdata    /data           ext4        defaults                  wait,length=-16384
/dev/block/bootdevice/by-name/cache       /cache          ext4        defaults                  recoveryonly
/dev/block/mmcblk0p1                      /sdcard         vfat        defaults                  recoveryonly
/dev/block/bootdevice/by-name/sec_efs     /efs            ext4        defaults                  recoveryonly
/dev/block/bootdevice/by-name/sec_efs     /sec_efs        ext4        defaults                  recoveryonly
/dev/block/bootdevice/by-name/carrier     /carrier        ext4        defaults                  recoveryonly
/dev/block/bootdevice/by-name/hidden      /preload        ext4        defaults                  recoveryonly

# FOTA
/dev/block/bootdevice/by-name/apnhlos     /modem          emmc        defaults                  recoveryonly
/dev/block/bootdevice/by-name/modem       /mdm            emmc        defaults                  recoveryonly
/dev/block/bootdevice/by-name/dsp         /dsp            emmc        defaults                  recoveryonly
/dev/block/bootdevice/by-name/vendor      /vendor         ext4        defaults                  recoveryonly
/dev/block/bootdevice/by-name/product     /product        ext4        defaults                  recoveryonly

# Add misc for GOTA
/dev/block/bootdevice/by-name/misc        /misc           emmc        defaults                  recoveryonly

# Samsung ODE
/dev/block/bootdevice/by-name/keydata     /keydata        ext4        defaults                  recoveryonly
/dev/block/bootdevice/by-name/keyrefuge   /keyrefuge      ext4        defaults                  recoveryonly

#Auto-generated code by FOTA Portal
/dev/block/bootdevice/by-name/dtbo	/dtbo	emmc	default	recoveryonly

After patching, I have converted dtbo.img to dtbo.img.lz4 using lz4 compression tool and created new recovery.img image with patched initrd file. After that. I have tried to flash magisk_patched.tar file with AP contents as one of the following: - Overwritten all three patched file in points 1, 2 and 3 above. -> Stuck at splash screen when trying to go to recovery after successfully flash with Odin. Download mode is appearing on splash screen. - Overwritten 1.boot.img and 2.dtbo.img.lz4 above. -> Successfully rooted but when trying to edit the system_root partition then I am facing the following problem:

D:\>adb shell
beyondxq:/ $ su
beyondxq:/ # mount -o rw,remount /system
beyondxq:/ # cd system
beyondxq:/system # echo "Test /system mounting" > temp.txt
beyondxq:/system # cat temp.txt
Test /system mounting
beyondxq:/system # cd ..
beyondxq:/ # mount -o rw,remount /system_root
beyondxq:/ # echo "Test /system_root mounting" > temp.txt
/system/bin/sh: can't create temp.txt: Read-only file system           ---> Error here
1|beyondxq:/ # cat system/temp.txt
Test /system mounting
beyondxq:/ # cat system_root/temp.txt
cat: system_root/temp.txt: No such file or directory              ---> Verify: File not created
1|beyondxq:/ # exit
1|beyondxq:/ $ exit

D:\>adb remount
Not running as root. Try "adb root" first.

D:\>adb root              ---> It didn't work as the next command is not working

D:\>adb remount                            
Not running as root. Try "adb root" first.

D:\>adb shell
beyondxq:/ $ su
beyondxq:/ # ls sdcard
Alarms Android DCIM Download Movies Music Notifications Pictures Podcasts Ringtones Samsung selinux_policy_modified
beyondxq:/ # mount -o rw,remount /system_root
beyondxq:/ # cp sdcard/selinux_policy_modified /system_root/sepolicy
cp: /system_root/sepolicy: Permission denied      ---> Permission Denied here
1|beyondxq:/ #

- Overwritten 1.boot.img and 2.dtbo.img.lz4 above with unpack and packed system.img.ext4.lz4 -> The result is boot-loop after successful flashing. Please suggest what went wrong or am I missing any step.

I have OnePlus 6T device which has A/B partition system and has a ROM of user type i.e [ro.build.type]: [user]. This device is rooted with Magisk. I have a requirement(Want to place customized sepolicy file under system_root directory ) to modify system.img. I have tried different tools like: 1. simg2img :

OMEN-by-HP-Laptop-15-dc0xxx:~/WorkArea/img-tools$ ./simg2img system.img sys.raw
Invalid sparse file format at header magi
Failed to read sparse file
OMEN-by-HP-Laptop-15-dc0xxx:~/WorkArea/img-tools$

2. imgtools

OMEN-by-HP-Laptop-15-dc0xxx:~/WorkArea/imgtool$ sudo ./imgtool system.img extract
[sudo] password for OMEN: 
system.img is not a recognized image. Sorry
OMEN-by-HP-Laptop-15-dc0xxx:~/WorkArea/imgtool$

3. and more tools even on windows.. but none of them is capable of parsing my system.img. I have copied system.img directly from OnePlus6T ROM setup which installs Android 9 on this device without any issue. Any help on: 1. How to fix the system.img so it will be extracted and repacked fine? 2. Any command that can unpack/repack system.img? 3. Any working tool to accomplish this task? **Update 1**: I have run file system.img and I found that its ext2 image and the tools support ext4.

system.img: Linux rev 1.0 ext2 filesystem data, UUID=d09c08e9-628d-590e-a610-3a14de2a8db0 (extents) (large files) (huge files)

**Update 2**: Tried to find the magic number and have following result:

OMEN-by-HP-Laptop-15-dc0xxx:~/WorkArea/imgtool$ xxd system.img | head
00000000: 0000 0000 0000 0000 0000 0000 0000 0000  ................
00000010: 0000 0000 0000 0000 0000 0000 0000 0000  ................
00000020: 0000 0000 0000 0000 0000 0000 0000 0000  ................
00000030: 0000 0000 0000 0000 0000 0000 0000 0000  ................
00000040: 0000 0000 0000 0000 0000 0000 0000 0000  ................
00000050: 0000 0000 0000 0000 0000 0000 0000 0000  ................
00000060: 0000 0000 0000 0000 0000 0000 0000 0000  ................
00000070: 0000 0000 0000 0000 0000 0000 0000 0000  ................
00000080: 0000 0000 0000 0000 0000 0000 0000 0000  ................
00000090: 0000 0000 0000 0000 0000 0000 0000 0000  ................
OMEN-by-HP-Laptop-15-dc0xxx:~/WorkArea/imgtool$

**Update 3** Fing the image already unpacked. So to add the required file, I have mount the image as sudo mount -o loop system.img system_mount and then tried to copy the contents to another folder with cp system_mount/* system/ so that I can add the required file and make new image out of it but I got following errors:

root@OMEN-by-HP-Laptop-15-dc0xxx:~/WorkArea# mkdir system && cp system_mount/* system/
cp: omitting directory 'system_mount/acct'
cp: cannot stat 'system_mount/bin': No such file or directory
cp: cannot stat 'system_mount/bt_firmware': No such file or directory
cp: cannot stat 'system_mount/bugreports': No such file or directory
cp: cannot stat 'system_mount/cache': No such file or directory
cp: cannot stat 'system_mount/charger': No such file or directory
cp: cannot stat 'system_mount/charger_log': No such file or directory
cp: omitting directory 'system_mount/config'
cp: omitting directory 'system_mount/d'
cp: omitting directory 'system_mount/data'
cp: omitting directory 'system_mount/dev'
cp: cannot stat 'system_mount/dsp': No such file or directory
cp: cannot stat 'system_mount/etc': No such file or directory
cp: cannot stat 'system_mount/firmware': No such file or directory
cp: omitting directory 'system_mount/lost+found'
cp: omitting directory 'system_mount/mnt'
cp: omitting directory 'system_mount/odm'
cp: omitting directory 'system_mount/oem'
cp: omitting directory 'system_mount/op1'
cp: omitting directory 'system_mount/op2'
cp: cannot stat 'system_mount/persist': No such file or directory
cp: omitting directory 'system_mount/postinstall'
cp: omitting directory 'system_mount/proc'
cp: cannot stat 'system_mount/product': No such file or directory
cp: omitting directory 'system_mount/res'
cp: omitting directory 'system_mount/sbin'
cp: cannot stat 'system_mount/sdcard': No such file or directory
cp: omitting directory 'system_mount/storage'
cp: omitting directory 'system_mount/sys'
cp: omitting directory 'system_mount/system'
cp: omitting directory 'system_mount/vendor'
root@OMEN-by-HP-Laptop-15-dc0xxx:~/WorkArea#

Hi guys I am setting up an android system for a company, one of the requirements is that "employees can't factory reset/ wipe out data of a device". I have already done the proper implementations on the OS itself. however I was looking throught the recovery.img and boot.img files to see if I could modify any xml file or anything to hide or set password auth for the factory reset and wipe options from the recovery. I know a guy with knowledge would be able to activate it back, however the average employee barely knows what recovery is, so it's really unlikely. It does not matter what type of recovery is needed to achieve this whether its an stock recovery or a twrp or cwm one. any ideas?

As https://superuser.com/revisions/1512700/2 explains, Windows supports this functionality:

Font substitution is set via the registry under the FontSubstitutes registry key at:

HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion\FontSubstitutes

Likewise, almost all desktop-focused Linux-based OSes do, with fc-alias. As an example, on my Fedora 40 KDE Spin installation:

fc-match monospace
fc-match sans-serif
fc-match serif

returns >

> NotoSansMono-Regular.ttf: "Noto Sans Mono" "Regular"
> NotoSans-Regular.ttf: "Noto Sans" "Regular"
> NotoSerif-Regular.ttf: "Noto Serif" "Regular"
>

However, I see absolutely no information online regarding whether the AOSP supports this functionality, nor how. Irrespective, I've reason to believe that support might exist, because when I view an HTML message via the official GMail, Outlook, and Proton Mail e-mail client applications with text content set to monospace, the typeface utilized appears to be monospace, and consistent across the clients.

I've developed a custom keyboard (IME) for Android that I can install and use on the device without any issues. The next step I want to take is to set this keyboard as the default input method in a custom AOSP build that I'm working on. I'm having trouble figuring out what changes I need to make in the AOSP source code to achieve this. Any guidance on how to make my custom keyboard the default would be really appreciated.

The carrier_list.textpb presented on this link: https://android.googlesource.com/platform/packages/providers/TelephonyProvider/+/master/assets/latest_carrier_id/carrier_list.textpb#4295 has wrong information for carrier_name for 2 carrier_id: carrier_id { canonical_id: 1608 **carrier_name: "Cosmofon"** carrier_attribute { mccmnc_tuple: "29402" } } carrier_id { canonical_id: 1609 **carrier_name: "Nov Operator"** carrier_attribute { mccmnc_tuple: "29403" } } This results with wrong information when using the source for android internet speed test application. What options do I have to change this source code?

I am building AOSP (version 14) from sources, for a PinePhone (so I have root access). I am trying to get reverse tethering to work (i.e. the Android device connects to the network through the other device over Ethernet). I can plug an Ethernet-over-usb adapter and see that a new network interface (eth0) appears in the output of ip link. This interface eth0 is ` but has state DOWN. It never gets in state UP` and it never gets an IP. In this situation on a Linux distro, I would just run a DHCP client for this interface. But on AOSP, I don't have a DHCP client to run from the command line (dhcpcd is no longer used in recent versions of Android, if I understand correctly). 1. Is there a way to manually run a DHCP server from the CLI? 2. What mechanism is supposed to handle this? On some phones and under some conditions (e.g. "the WiFi is not connected"), then plugging an Ethernet cable into the Android device "just works". What should I do in my AOSP build to make this "just work" for all eth* interfaces that may appear?

I want to build AOSP from source, build Linux kernel from sources and run all of this in android emulator. Later I need to make some experiments, for which I need to modify sources, so this is why i need to build all the code from sources. I am doing repo init --partial-clone -b main -u https://android.googlesource.com/platform/manifest (I have tried main branch and android 14 branch...), then repo sync, lunch some target (I have tried miscellaneous ones) then "m", then trying to run emulator. And at this moment I have a problem: the emulator cannot start. Basically, there are two reasons for that: * Kernel is unable to decompress LZ4-compressed image (I unpack the image by hands, but this not helps, see next issue); * Kernel is unable to mount file systems. This may happen because kernel doesn't have DTB (which dtb on x86_64???) Also, I found, that by default emulator uses not a kernel from "out" directory, but some other. I specify in command line (via -kernel option) the kernel found in "out" directory, but this not helps. * for -eng builds, emulator complains on absence of user-data.img file; * for userdebug builds, emulator is unable to mount root or some other partitions (linux kernel starts, but init process aborts with error message). I'm looking for instruction how can I make x86_64 build which will run in the emulator. Maybe I need some particular target or some particular branch?

I've got a Google Pixel 8 Pro running GrapheneOS. When I'm on the phone talking to somebody and hold the phone to my ear, it very often accidentally registers taps. This e.g. leads to activation of the flashlight or Bluetooth by the slide-down menu. Locking the screen after answering the call does not help, probably because the slide-down menu is accessible anyway. I cannot find any setting to prevent this. Does anyone have the same issue or any idea of how to fix this? I used the app Sensors Toolbox to check whether the proximity sensor works as it should. And it does. However, it only detects small distances at the top of the phone (where the ear should be during the call, which is not always the case). If the phone detects a small distance to the skin during the call, the screen is deactivated, but is activated if the phone slips a little from that position. Is this normal?

I am currently using Google Pixel 8. I am trying to download the AOSP kernel, compile it, and flash it into my device. I followed the instructions from the document below. https://source.android.com/docs/setup/build/building-pixel-kernels#pixel-gki-kernel-branches . I used the right combinations for my device and was able to compile and build the kernel using Kleaf. Then, I went to fastboot mode and flashed my device using the commands below.

fastboot flash boot        out/shusky/dist/boot.img
fastboot flash dtbo        out/shusky/dist/dtbo.img
fastboot flash vendor_kernel_boot      out/shusky/dist/vendor_kernel_boot.img
fastboot reboot fastboot
fastboot flash vendor_dlkm out/shusky/dist/vendor_dlkm.img
fastboot flash system_dlkm out/shusky/dist/system_dlkm.img

After these commands, the device was left in fastbootd mode. What should I do to start my Pixel 8 with the built kernel? It seems when I simply reboot the device, it gets back to its original kernel.

I'm trying to build Android 13 (ARM64) for the Android emulator (linux/aarch64). I managed to correctly start Android 12 (ARM64) images with the following setup, but I fail to do the same for Android 13. 1. I build the source code with lunch target lunch sdk_phone_arm64-userdebug and the following build command on a x86_64 server: "source ./build/envsetup.sh && lunch sdk_phone_arm64-userdebug && m && m emu_img_zip" 2. I then copy/unzip the emulator image artefacts to my linux arm64 machine using the zip file in the build out directory under: "out/dist/sdk_phone_arm64-img-eng.ubuntu.zip" 3. I use the lastest emulator binary for linux aarch64 from: https://ci.android.com/builds/branches/aosp-emu-master-dev/grid?legacy=1 4. I then try to start the emulator with the following command: ` /android/sdk/emulator/emulator -avd Arm64 -no-window -no-snapshot -ports "5556,5557" -grpc "8556" -skip-adb-auth -no-snapshot-save -logcat "*:V" -show-kernel -logcat-output "/tmp/android-unknown/logcat.log" -shell-serial "file:/tmp/android-unknown/kernel.log" -no-boot-anim -wipe-data -gpu swiftshader_indirect -qemu -append "panic=1" -cpu max -machine gic-version=max & ` For Android 12 this setup and commands work well and the emulator starts correctly. However, for Android 13 the emulator gets stuck when trying to load the images. The kernel is stuck in an endless reboot and shows the following error:

kernel: [    1.346161][    T1] uart-pl011 9000000.pl011: no DMA platform data
kernel: [    1.349940][    T1] VFS: Cannot open root device "(null)" or unknown-block(0,0): error -6
kernel: [    1.350060][    T1] Please append a correct "root=" boot option; here are the available partitions:
kernel: [    1.350306][    T1] 0100            8192 ram0 
kernel: [    1.350383][    T1]  (driver?)
kernel: [    1.351598][    T1] 0101            8192 ram1 
kernel: [    1.351617][    T1]  (driver?)
kernel: [    1.351711][    T1] 0102            8192 ram2 
kernel: [    1.351723][    T1]  (driver?)
kernel: [    1.351808][    T1] 0103            8192 ram3 
kernel: [    1.351820][    T1]  (driver?)
kernel: [    1.351906][    T1] 0104            8192 ram4 
kernel: [    1.351917][    T1]  (driver?)
kernel: [    1.352000][    T1] 0105            8192 ram5 
kernel: [    1.352011][    T1]  (driver?)
kernel: [    1.352094][    T1] 0106            8192 ram6 
kernel: [    1.352106][    T1]  (driver?)
kernel: [    1.352185][    T1] 0107            8192 ram7 
kernel: [    1.352196][    T1]  (driver?)
kernel: [    1.352274][    T1] 0108            8192 ram8 
kernel: [    1.352285][    T1]  (driver?)
kernel: [    1.352365][    T1] 0109            8192 ram9 
kernel: [    1.352376][    T1]  (driver?)
kernel: [    1.352469][    T1] 010a            8192 ram10 
kernel: [    1.352480][    T1]  (driver?)
kernel: [    1.352571][    T1] 010b            8192 ram11 
kernel: [    1.352582][    T1]  (driver?)
kernel: [    1.352744][    T1] 010c            8192 ram12 
kernel: [    1.352760][    T1]  (driver?)
kernel: [    1.352847][    T1] 010d            8192 ram13 
kernel: [    1.352860][    T1]  (driver?)
kernel: [    1.352962][    T1] 010e            8192 ram14 
kernel: [    1.352974][    T1]  (driver?)
kernel: [    1.353063][    T1] 010f            8192 ram15 
kernel: [    1.353075][    T1]  (driver?)
kernel: [    1.353296][    T1] Kernel panic - not syncing: VFS: Unable to mount root fs on unknown-block(0,0)
kernel: [    1.353515][    T1] CPU: 2 PID: 1 Comm: swapper/0 Not tainted 5.15.41-android13-8-00030-gc66cde32ee51-ab8840540 #1
kernel: [    1.353688][    T1] Hardware name: linux,ranchu (DT)
kernel: [    1.353866][    T1] Call trace:
kernel: [    1.353921][    T1]  dump_backtrace.cfi_jt+0x0/0x8
kernel: [    1.354014][    T1]  dump_stack_lvl+0x80/0xb8
kernel: [    1.354083][    T1]  panic+0x180/0x444
kernel: [    1.354140][    T1]  mount_block_root+0x1ac/0x270
kernel: [    1.354206][    T1]  mount_root+0x68/0x90
kernel: [    1.354257][    T1]  prepare_namespace+0x164/0x1e8
kernel: [    1.354321][    T1]  kernel_init_freeable+0x120/0x19c
kernel: [    1.354390][    T1]  kernel_init+0x40/0x36c
kernel: [    1.354528][    T1]  ret_from_fork+0x10/0x20
kernel: [    1.354844][    T1] SMP: stopping secondary CPUs
kernel: [    1.355408][    T1] Kernel Offset: disabled
kernel: [    1.355480][    T1] CPU features: 0x2,200011e3,20000846
kernel: [    1.355630][    T1] Memory Limit: none
kernel: [    1.368911][    T1] Rebooting in 1 seconds..

It seem that for some reason the root fs can't be correctly mounted. However, with Android 12 images this works fine. So how do I need to adjust the build and starting process for Android 13 images? **Update**: If I used the additional sdk module the kernel detects the partitions but avb fails: "source ./build/envsetup.sh && lunch sdk_phone_arm64-userdebug && m && m emu_img_zip"

kernel: [    2.326708] EXT4-fs (vdd1): recovery complete
kernel: [    2.328027] EXT4-fs (vdd1): mounted filesystem with ordered data mode. Opts: errors=remount-ro,nomblk_io_submit. Quota mode: none.
kernel: [    2.331535] init: [libfs_mgr]check_fs(): mount(/dev/block/pci/pci0000:00/0000:00:06.0/by-name/metadata,/metadata,ext4)=0: Success
kernel: [    2.340460] init: [libfs_mgr]umount_retry(): unmount(/metadata) succeeded
kernel: [    2.342534] init: [libfs_mgr]Not running /system/bin/e2fsck on /dev/block/vdd1 (executable not in system image)
kernel: [    2.346563] EXT4-fs (vdd1): mounted filesystem with ordered data mode. Opts: . Quota mode: none.
kernel: [    2.349029] init: [libfs_mgr]__mount(source=/dev/block/pci/pci0000:00/0000:00:06.0/by-name/metadata,target=/metadata,type=ext4)=0: Success
kernel: [    2.352748] init: Failed to copy /avb into /metadata/gsi/dsu/avb/: No such file or directory
kernel: [    2.356374] init: [libfs_mgr]Created logical partition system on device /dev/block/dm-0
kernel: [    2.359123] init: [libfs_mgr]Created logical partition system_dlkm on device /dev/block/dm-1
kernel: [    2.362074] init: [libfs_mgr]Created logical partition system_ext on device /dev/block/dm-2
kernel: [    2.364862] init: [libfs_mgr]Created logical partition product on device /dev/block/dm-3
kernel: [    2.367299] init: [libfs_mgr]Created logical partition vendor on device /dev/block/dm-4
kernel: [    2.369287] init: DSU not detected, proceeding with normal boot
kernel: [    3.376310] init: [libfs_avb]Device path not found: /dev/block/by-name/system
kernel: [    3.378664] init: [libfs_avb]Fallback to use logical device path: /dev/block/dm-0
kernel: [    4.384217] init: [libfs_avb]Device path not found: /dev/block/by-name/system
kernel: [    4.385757] init: [libfs_avb]Fallback to use logical device path: /dev/block/dm-0
kernel: [    4.388395] init: [libfs_avb]total vbmeta size mismatch: 6720 (expected: 6208)
kernel: [    4.396205] init: [libfs_avb]Failed to verify vbmeta digest
kernel: [    4.397695] init: [libfs_avb]vbmeta digest error isn't allowed 
kernel: [    4.399311] init: Failed to open AvbHandle: No such file or directory
kernel: [    4.400961] init: Failed to setup verity for '/system': No such file or directory
kernel: [    4.402834] init: Failed to mount /system: No such file or directory
kernel: [    4.404555] init: Failed to mount required partitions early ...
kernel: [    4.415023] init: InitFatalReboot: signal 6
kernel: [    4.425984] init: #00 pc 000000000031f8c8  /init (UnwindStackCurrent::UnwindFromContext(unsigned long, void*)+88)
kernel: [    4.427662] init: #01 pc 0000000000311b7e  /init (android::init::InitFatalReboot(int)+94)
kernel: [    4.429092] init: #02 pc 0000000000312033  /init (android::init::InstallRebootSignalHandlers()::$_24::__invoke(int)+19)
kernel: [    4.431357] init: #03 pc 00000000004d99d0  /init (__restore_rt)
kernel: [    4.432597] init: #04 pc 00000000004ce77e  /init (abort+190)
kernel: [    4.433782] init: #05 pc 0000000000317ceb  /init (android::init::InitAborter(char const*)+27)
kernel: [    4.435544] init: #06 pc 000000000048aecc  /init (android::base::SetAborter(std::__1::function&&)::$_3::__invoke(char const*)+60)
kernel: [    4.438285] init: #07 pc 000000000048a69e  /init (android::base::LogMessage::~LogMessage()+350)
kernel: [    4.440081] init: #08 pc 0000000000307012  /init (android::init::FirstStageMain(int, char**)+10354)
kernel: [    4.441980] init: #09 pc 00000000004c5cce  /init (__real_libc_init(void*, void (*)(), int (*)(int, char**, char**), structors_array_t const*, bionic_tcb*)+718)