For non-technical users, is there a one-click way to get rid of the Amazon stuff & install stock Android? I am trying to help a friend on another continent who has a Kindle Fire 7 running OS v 5.6.8 (auto-updated just a few days ago, which looks like it might be a problem). Solutions seem to involve downloading scripts to a PC, then using Android Studio to side-load the scripts to the Kindle, then running them, which would be beyond my friend, even with assistance - even if they had a PC, which they do not (nor access to one), just the Kindle Fire. Does anyone know of a one-click solution, or something close to it, involving only the Kindle Fire (7 OS 5.6.8)?

I've encountered apps which create global Android context menu entries. *Librera Reader * *Poet Assistant * --- Suggesting to uninstall apps isn't an answer. Using ADB is fine. One may also want to remove some of the default Android options such as 'cut' (for text). LineageOS 21 / Android 14. The screenshots are from Firefox version 130.0.

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?"

Imagine the following situation: - The vendor of my phone has stopped providing security patches for the stock OS. - The HW is perfectly fine and powerful enough for years to come, so I'm definitely not willing to replace it just to get access to security patches. - Running a phone OS with unfixed security vulnerabilities makes me uneasy. (It feels insane enough to run a computer at home with an OS that's a year behind on security patches. It's twice as insane to do the same with a device that I routinely take to all kinds of hostile environments and untrusted networks.) - Authors of all kinds of random apps have grown a habit of requiring SafetyNet attestation. - I don't need root access to my phone, and I can live with losing some of the proprietary vendor-provided features. I also don't care too much about running the latest Android version, as long as it's receiving security fixes and is compatible with most apps. I know I have the following two options: - Stick to the stock vendor OS, which is gradually going to become full of security holes. However, SafetyNet passes and I can run all kinds of apps because they feel safe on my device. - Install a custom OS. This will fail SafetyNet, unless I use a tool to hack around it and try to pretend the phone is not rooted. This approach is likely to stop working at some point, leaving me with a device that fails SafetyNet. Thus although my device may have up-to-date security patches, apps will refuse to run because they deem the device insecure. **Is there a third way, which would let me stay up-to-date on security patches while not breaking SafetyNet?** I can imagine something like a pure AOSP system, perhaps built and signed by Google or another vendor, that I could run unrooted and unmodified (relying on vendor drivers through the Treble thing).

I have Micromax Canvas HD 116 with Android 4.2.2 installed on it. What I hate is the unnecessary software offered by them, which is not only occupying space but also RAM and affecting the speed of the device. I just want to get rid of those bloatware somehow. I know if I follow some good rooting procedure, I can achieve it. But is there any way, or an official way so that I can manually re-install the original pure Android OS on my device? I would be very much obliged if someone would provide some good resources about it, and which is applicable to any device.

I always thought that com.google.android.packageinstaller or pm would refuse to install an .APK if its manifest didn't include reverse DNS for the package name. However, adb shell cmd package list packages returns package:android within the list of standard package names. It's the sole exception, which actually makes it more startling. Within comparable package managers which utilize such a structure (like flatpak) the rDNS is mandatory in the package manifest. I expected pm to be the same. Consequently: - Is this rule true for applications which the user installs but not the system, perhaps? Or - Can a package merely be named anything, yet the convention exists due to the Play Store, or another driving force within the ecosystem?

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 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?

On Motorola Edge 30, the system setting for this is not working. Interestingly, I found a GitHub issue that suggests this might be a bug in Android 13. Is there a workaround or a reliable way to detect specifically when an outgoing call is answered in Android 13?

I need to examine how the ELF binary (which is compiled for ARM processor) executes on Android-arm64. Can you please suggest how I can emulate Android-arm64 on the x86 system? I have checked Android studio, but it seems that it only runs a single application but not the whole Android system.

I have a Chinese HUAWEI Honor 4A and want to install a different OS without the bloatware and restrictions that come with it (eg no play store). Any recommendations on which path to choose? I just want a simple, stable, hassle free OS and the tips on the right way to do it.

I have a Samsung Galaxy S3 I9300 running CyanogenMod 11 (Android 4.4.4). Over time I have noticed that most of my system stability issues are because Android appears to have a "timeout" period for tasks, and if a task does not respond within a certain time (e.g. when I try to load a web page with enough Javascript to put significant load on a latest generation Mac), the OS declares that the task has hung and axes it. This has been happening with increasing frequency as mobile websites have been expecting me to have an increasingly powerful phone, e.g. it does not happen on my Samsung Galaxy S5 nor on a friend's Galaxy S6 Edge. I tried looking under my sysctl and build settings on System Tuner for a setting that controls this "activity response timeout" but couldn't find any. Is there a way to increase this timeout?

Flashing the ARM64 version (Android 11 or 12) from [here](https://developer.android.com/topic/generic-system-image/releases) works fine on my Blackview BL6000 Pro. However, flashing any ARM64+GMS only boots into the bootloader (not fastbootd). In general, how would one investigate why this happens? I can boot into the Stock Recovery, however, I cannot adb into the device because it shows up as unauthorized (perfectly authorized in the OS though). Unfortunately, afaik there's also no custom recovery available for my device. I thought about reading logcat or dmesg but I don't see a way to access them without having adb access. Thanks for any hints. Here's my procedure: 1. SP Flash the stock rom 2. Unlock the bootloader in the dev options 3. adb reboot bootloader 4. fastboot flashing unlock 5. fastboot reboot fastboot 6. fastboot delete-logical-partition product(this is necessary because the GSI is larger than the stock rom system partition) 7. fastboot erase system 8. fastboot flash system aosp-system.img (automatically resizes system) 9. fastboot -w 10. fastboot reboot which lands me in the OS for the non-GMS version, and in the bootloader for the GMS version.

The native calculator app on Android 4.4 has a "Clear history" option, but I have no clue on how to see this history. I've tried swipe movements, clicked on every possible button, and even held down the menu button as described [here]( https://android.stackexchange.com/questions/19407/accessing-calculation-history-on-htc-calculator-app) , but I could not make the on-screen keyboard show up. Has anybody had more luck trying this?

**Intro:** I had an issue getting the build to compile, but finally got it to successfully build/compile, & installed on my phone, as covered here: https://android.stackexchange.com/questions/239240/mkbootfs-command-not-found-while-trying-to-build-aosp-kernel?noredirect=1#comment317565_239240 I followed the guide here: https://source.android.com/setup/build/building-kernels BUT... I made **NO CHANGES to the kernel** as I want it to work first. My phone boots fine, but the touchscreen doesnt work! Am I missing something? To say it again if I wasn't clear, I have vanilla AOSP Android 11, made no changes, compiled the kernel, flashed it to my phone, and the touchscreen doesnt work. If I can't figure this out, at least I'm sharing a complete guide on how to build this...without a functional touch screen! Here's exactly what I did: **PREREQS:**

Unlock bootloader (not covered here)

Install kernel-build-tools (not included in repo for some reason):
cd ~/
mkdir kernel-build-tools
git clone https://android.googlesource.com/kernel/prebuilts/build-tools 
ls -l kernel-build-tools
nano ~/.profile
Add lines to path: (this will work as current user NOT SUDO!!)
# add Kernel tools to path
if [ -d "$HOME/kernel-build-tools/build-tools/linux-x86/bin" ] ; then
    PATH="$HOME/kernel-build-tools/build-tools/linux-x86/bin:$PATH"
fi
Refresh environment: source ~/.profile

Install/Setup adb & fastboot
Download adb & fastboot & unzip:
wget https://dl.google.com/android/repository/platform-tools-latest-linux.zip 
sudo apt-get install unzip
unzip platform-tools-latest-linux.zip -d ~
nano ~/.profile
Add lines:
# add Android SDK platform tools to path
if [ -d "$HOME/platform-tools" ] ; then
    PATH="$HOME/platform-tools:$PATH"
fi
Update environment: source ~/.profile

Install build tools:
sudo apt-get update
sudo apt-get install -y bc bison build-essential ccache curl flex g++-multilib gcc-multilib git gnupg gperf imagemagick lib32ncurses5-dev lib32readline-dev lib32z1-dev liblz4-tool libncurses5 libncurses5-dev libsdl1.2-dev libssl-dev libxml2 libxml2-utils lzop pngcrush rsync schedtool squashfs-tools xsltproc zip zlib1g-dev

Create build directories:
mkdir -p ~/bin
mkdir -p ~/android/lineage

Install Repo cmd:
curl https://storage.googleapis.com/git-repo-downloads/repo  > ~/bin/repo
chmod a+x ~/bin/repo

Fix Python:
sudo ln -s /usr/bin/python3 /usr/bin/python

Configure Git:
git config --global user.email "[email]"
git config --global user.name "[user]"

Turn on Caching to speed up build:
export USE_CCACHE=1
export CCACHE_EXEC=/usr/bin/ccache
ccache -M 25G

**STEPS:**

AOSP REPO:
cd ~/
mkdir aosp && cd aosp
repo init -u https://android.googlesource.com/platform/manifest  -b android-11.0.0_r38 --depth=1
repo sync

AOSP KERNEL REPO:
cd ~/
mkdir aosp-kernel && cd aosp-kernel
repo init -u https://android.googlesource.com/kernel/manifest  -b android-msm-bonito-4.9-android11-qpr2
repo sync

KERNEL CONFIGS: (I did NOT do this; left here for reference for others)
ls -l ~/android/aosp-kernel/build.config -> [symbolic path to actual file]
->~/android/aosp-kernel/private/msm-google/build.config.bonito_no-cfi
Edit this file:
(orig) POST_DEFCONFIG_CMDS="check_defconfig && update_nocfi_config" ->
POST_DEFCONFIG_CMDS="update_nocfi_config"
*Note: This file indicates the kernel config file: bonito_defconfig
Edit & add to: ~/android/aosp-kernel/private/msm-google/arch/arm64/configs/bonito_defconfig
# Kevin added - IPTables TTL support
CONFIG_NETFILTER_XT_TARGET_HL=y 
CONFIG_NETFILTER_XT_TARGET_HMARK=y
[Need a blank carriage return at bottom!]

BUILD Image.lz4 via AOSP Kernel repo: (I tried both)
build/build.sh
-OR: BUILD_CONFIG=./private/msm-google/build.config.bonito_no-cfi build/build.sh (if you want to specify a different build that the default)

CONVERT Image.lz4->boot.img via AOSP repo:
Copy newly created \aosp-kernel\out\android-msm-pixel-4.9\dist\Image.lz4
-> \aosp\device\google\bonito-kernel\
cd ~/android/aosp
source build/envsetup.sh
Setup device:
lunch aosp_sargo (Just lunch to get device list)
Make only boot image:
m bootimage

FLASH TO PHONE:
adb reboot bootloader
fastboot flash boot boot.img
fastboot reboot

I have Android v85a bought from China. It has FuntouchOS installed. I want to change that to some latest compatible version of Android from Google. Is it possible?

Are the AOSP Email (com.android.email) and Calendar (com.android.calendar) apps dead? I cannot find any information on their development, though they appear to have been stuck on version 6.0.1 for some time. They are still distributed as part of CyanogenMod.

The way the Google support page ("Android 8.1 and up") is written suggests that this option may have been only available in third-party ROMs: > **Disable apps that came with your phone** > > You can’t delete some system apps that came pre-installed on your > Android phone. But on some phones, you can turn them off so that they > won't show on the list of apps on your phone. To learn how to disable > apps, contact your device manufacturer. I don't personally have an issue with bloatware as I run LineageOS, but temporarily turning off apps would have often been beneficial for various reasons (some, while useful, are rarely used and may run at boot; issues with the latest update and no roll-back option).

I am trying to find the "message sent" "blip" sound specifically

First, I'm currently using Android 6.0 on a Nexus 5, although this issue was already present when I was using Android 5.0. Now I'll explain what I mean by "not seeing the warning bar". Regularly, the **Settings > Data usage** screen looks like this. You can visibly see the warning bar, and that it is set to 4.7 GB. Now, the **Settings > Data usage** screen on *my* device looks like this: As you can see, there is no warning bar, and also no greenish graph that shows my recent cellular data usage. How it happened, you ask? Well, it's a (more than a-) little silly. Usually, to change the warning bar, you hold on to it by pressing it, and then you slide up or down to increase or decrease the warning limit. I got a little bored I guess, pressed the warning bar, and started to continually raise it, as I was interested in the upper limit that Google enables. I took some time, but After getting to between 1.0E8 and 1.0E9 (it was hard to tell, since that number was rapidly increasing on my screen), it went back to 0, and started increasing from 0 again. I was satisfied with my discovery, and wanted to try to stop the warning bar as close as possible before it resets to 0. After a few attempts where I came closer to achieving my goal, I accidentally lifted up my finger a bit while I was increasing the warning bar's limit. At 'normal' limits, nothing happens, and you can continue changing the limit afterwards. But when I lifted my finger up, my limit was in the range of tens of millions of GB. And when I lifted it in the middle of continually increasing the warning bar, the bar just disappeared, and with it, the graph. My guess is that the bar was set so high, so the amounts of cellular data I use are insignificant compared to it, and that's way no graph is shown. But why can't I see the warning bar? Anyway, this happened a few months ago, when my Android version was 5.0. I searched on this issue, but haven't found anyone else that encountered my problem. Also, before posting this question, I tried to reenact my scenario on another friend's Nexus 5 (running Android 5.1.1), to maybe gain more information about what happened on my device. A minute of experimenting later, his warning bar vanished too. Any idea how can I resurrect the warning bar? (preferably without rooting the device or another 'drastic measure')