I have a dead phone that can have its flash memory accessed via BROM MtkClient, it can be read and written to, but the phone doesn't turn on. Rebooted one time and it didn't turn back on. Seems to be a problem with a charging circuit/board that could be replaced. Is there a way to run some tests on the mainboard via something like MtkClient or some other method using BROM to find out if CPU, RAM, etc. are OK? Thanks.

I've seen this with plenty of smartphones,usually after 1-2 years of use.The phone overheats for a minute or 2 before cooling down,but it's performance doesn't differ from a non-overheating phone that has been powered on. Is this simply due to the natural wear and tear which causes a CPU overload for the first few minutes,or it it because of the failing/malfunctioning of a particular component in the phone/(which would in turn, adversely affect its battery life)

I have a 4yr old phone and it's CPU processor can take up to 6GB RAM, but I have the model with 3GB of RAM and it's somewhat slow in doing some tasks that are high demanding. So, after I root the phone using Magisk and use Roehsoft RAM Expander and my SD card to expand it to 6GB RAM, if I unroot my phone back, will the virtual RAM still remain or will it get left behind?

This question might be redundant or a possible duplicate, but I use an NDK library that runs only on ARM devices. Is there a way I could know what percentage of Android devices my app can support based on CPU architecture just like these statistics on Android Platform Versions ? My goal is to ascertain the number of devices my app won't support.

/sys/devices/virtual/thermal/thermal_zone0/temp shows 37°C (37000 millicelcius) no matter what the actual temperature is. The device is Moto G32, Android 12, not rooted. Using cat on Termux to view the temperature.

I have a Xiaomi Redmi Note 4 S625 global variant (4/64GB). A day or so ago, I noticed a quick battery drain (from 100% to 24% after a whole night idle and 2-3 hours of heavy use the next day) and from there, it was dropping a percent every 2nd-3rd minute. It never happened before as it's a 4000mAh battery and usually lasts around 2 days on normal use. I'm new to the smartphone world and I was reading online about the usual causes of battery drain including background apps consuming it and overcharging issues damaging the battery. I got worried as last night it was indeed left plugged in for like 2-3 hours maybe after a full charge. So either the battery is damaged due to overcharging, or it's some software issue. Now what I noticed is the CPU usage is maxed with no app running in the background. I don't know if CPU-Z's usage info is accurate, but it's 100% when the battery is like 15% or lower and 40-50% when the battery is 20% or above. Maybe there's some background process or maybe it's normal, I don't know. I'm pretty clueless at this point. Here's a screenshot of CPU-Z: Really appreciate it if anyone helped me with this one. Thanks.

This file sync app is active for 8 seconds, keeps awake for zero seconds, and yet uses 25-30% of power in a given day. **What could an app be doing to drain battery, *without* showing up as CPU use time?** To be clear, I'm not looking for solutions to *this specific* problem (talking to the dev for that): I'm looking for info on what apps can do that isn't logged in battery usage. Something is clearly happening, but what? (Phone is Poco F1, latest updates on everything)

There are a variety of CPU architectures that android systems use such as

-v8a

,

-v7a

,

,

and

. Is there a way for

or any other tool to detect the architecture of a connected device? I have many devices connected to a PC running adb and I would like to create a script so that

can deliver the correct package. For example, I have packages

-v8a.apk

,

-v7a.apk

and

.apk

on my desktop that correspond to their respective architectures as well as tens of android devices that are connected to an

server on desktop. How can I iterate the output of

devices

so that the script figures out the architecture of each android device and automatically install the right apk to each device?

So I recently rooted my Pixel 6 (Android 13) using Magisk and tried to control the CPU frequency, but it did not have userspace CPU governor. I tried to set scaling_setspeed in /sys/devices/system/cpu/cpu0/cpufreq/ with no luck. Also tried setting scaling_max_freq and scaling_min_freq using the maximum frequency and scaling_governor as performance mode, but when workloads start, the frequency would drop. Is there a way to set and fix the frequency without installing userspace CPU governor? It was to my understanding that performance mode would keep the CPU at max frequency, but even then, that was not the case.

I am trying to run Docker on Android, using a Pixel 3a XL rooted, running stock rom but flashed a custom kernel. I need to enable cpu, cpuset, memory, io, and pid controllers in cgroupv2. After enabling them in menuconfig and flashing the kernel, the script used to check shows only pid available under cgroupv2 controllers. What do I need to do besides enabling these options in the kernel’s menuconfig? Did I maybe not enable all the necessary options? Any help would be greatly appreciated! With the current state, when I run docker I get a warning for each item, ex “WARN: Unable to find cpu controller”. and error setting cgroup config for procHooks process: bpf_prog_query(BPF_CGROUP_DEVICE) As I understand it, these options may be mounted with cgroupv1 and this is why they do not show up? I am using this guide: https://gist.github.com/FreddieOliveira/efe850df7ff3951cb62d74bd770dce27 and these are the options I enabled in my kernel using menuconfig: https://wiki.gentoo.org/wiki/Docker From the config I flashed in my kernel:
CONFIG_CGROUPS=y
CONFIG_CGROUP_FREEZER=y
CONFIG_CGROUP_PIDS=y
CONFIG_CGROUP_DEVICE=y
CONFIG_CPUSETS=y
CONFIG_CGROUP_CPUACCT=y
I flash the kernel by flashing the **Image.lz4-dtb** file that is created after building the kernel. Here is a photo after running the script to check if kernel options are all enabled. Am trying to change these from missing to available/enabled.

There is a very similar question on this site but it is outdated and contains no/outdated statistical sources. I want to know how is the market divided between arm64-v7a, arm64-v8a, armeabi (I know it's deprecated now), x86, etc... The best answer would be if there is some statistic made that shows the percentages of each type. The reason I am asking is because I am a mobile developer and I want to know if I make an app that runs on 64-bit processors only, then what percentage of people won't be able to use the app.

Firebase has physical devices for testing: https://firebase.google.com/docs/test-lab/android/available-testing-devices however it's a little expensive. I was wondering if testing things on a physical Android device is a real thing and if there are frameworks for that. I know that there are unit tests that are mocked and run on the computer, but some things like the Android Media Codec Decoder can only be tested on the device

Given the fact I have rooted device, is there a way to get that data? Raw or w/ tools. P.S. I was looking around for a build of htop with cpu thermals but I dont think there is any compatible for Android.

I was reading [this blog post](https://handstandsam.com/2016/01/28/determining-supported-processor-types-abis-for-an-android-device/) on determining the supported ABIs for a phone. It said that, prior to Lollipop, the command is

getprop ro.product.cpu.abi

whereas, after Lollipop, it's

getprop ro.product.cpu.abilist

My phone is running Android 11 and I note that both properties are supported by getprop. Specifically, abi is arm64-v8a and abilist is arm64-v8a,armeabi-v7a,armeabi. Is the support on post-Lollipop devices for getprop ro.product.cpu.abi just for backwards compatibility and, hence, abi is just returning the first item in abilist or does the abi value hold more significance?

My Samsung Galaxy S8 (SM-G950F) is not showing the developer option to "Show CPU usage". I have turned the "Developer options" on, but scrolling down to "Monitoring" I only get 2 options: "Strict mode enabled" and "Profile GPU rendering". I don't know why is it not available and how can I get it. I keep getting a message "Abnormal account. You need to login again." about every 15 minutes on my screen, but I have no idea which app is doing this, so I'm trying to track it.

To find the number of cores available to you in Termux you run: grep Cpus_allowed /proc/self/status This number of cores is limited in a similar way to running taskset on GNU/Linux. I am trying to be able to predict what that will return. According to the app CPU-Z my phone (Huawei Smart P) has 1 HiSilicon Kirin 659 with 8 cores. According to the app CPU Info 4 cores are running the same speed (480-1709Mhz) and 4 cores are running the same speed (1402-2362Mhz). After booting the phone and waiting 5 minutes to make sure all startup tasks have been started/completed I started Termux, login through ssh and got: Cpus_allowed_list: 0-7 Which is exactly what I expect. But if I press the home key, I get: Cpus_allowed_list: 2-3 I thought this might have to do with how hard the cores are loaded, so I switched to Termux again, started 16 bzip2s. This does not change the number of cores I get immediately. But after 30s I get 4 cores: Cpus_allowed_list: 0-3 And yet later I get bumped back to 2 cores: Cpus_allowed_list: 2-3 This behaviour happens through ssh whether Termux is in the foreground or background. The effect of the home key is only when running Termux: If I run CPU Info, then press home and then start Termux, then Termux still has 8 cores: Cpus_allowed_list: 0-7 Only when I switch away from Termux using the home key, the app-list key, or the back key does the number of CPUs change. Software controlled big.LITTLE could explain going from 8 to 4 cores if the limit was not enforced immediately after boot, but only activated later. Since the limit is not activated 5 minutes after boot, I think it is safe to reject this as the explanation. Also it does not explain limiting to 2 cores some of the time when running 16 bzip2s. What is causing the phone to limit me from using 8 cores? How can I tell the phone not to do so? What is causing the limit to jump between 2 and 4 cores at seemingly random intervals? (On top of this I had expected the cores to run at 100% speed which also does not happen). The limitation does _not_ happen if not run through ssh or if run in a tmux session where the tmux session is started via the terminal on the phone.

Since quite some time I am having some peculiar performance problems on my Motorola Moto X Force. Sometimes any interaction (like just opening Chrome for example) takes incredibly long until it responds. This also happens after clearing all apps in the task switcher and it can also happen pretty soon after rebooting the phone. Imho a phone with a 4x 2.00GHz Cortex-A57 + 4x 1.50GHz Cortex-A53 (Qualcomm MSM8994 Snapdragon 810, 64bit) and 3 GiB RAM should not have such problems. Thinking some app might hog the CPU in the background (though I do not have any battery problems - it can go for over 48 hours without charging) I installed some system monitoring apps in order to get to the bottom of this. One app, [System Monitor Lite](https://play.google.com/store/apps/details?id=com.cgollner.systemmonitor.lite) has the ability to log in the background, when enabled. I wanted to check if I can correlate CPU or RAM usage with the periods where the phone runs slow. _However_ once the background logging of that app is active, the phone immediately runs noticeably smoother! And it runs smooth as long as the background logging is active. Once I turn it off, the phone will get slow again after some time. This makes me think now that this phone (or Android 7.0) has a power management problem. i.e. letting the CPU(s) run in a low performance state, when it should not. Has anyone else ever experienced something like that or any ideas how to combat this?

I'm suspecting that Android sometimes limits my CPU at around 66% when the temperature is too high. I can see that my Geekbench score is much lower than what it should be: Even though my CPU isn't supposed to be throttled: How can one find out whether Android is limiting my CPU, e.g. because the temperature is too high? I use a Samsung Galaxy S9 with Android 10.

I am using CPU-Z to test basic things about the J7. It reports an Exynos Octa 7580, 8 cores, 8x ARM Cortex-A53 @ 1.5GHz, r0p3, 28 nm. At all times that I checked, only cores 0-3 are active, and cores 4-7 are stopped. Power saving is disabled. **Is there any way of activating all cores?** **Is there any way of at least seeing all of them active, for testing purposes?** I have found a few posts around (here and here ) mentioning that it may be the way the phone + OS kernel keep temperature in check, but I am not sure it applies to J7, and if so, how to circumvent it. **PS:** I find some times that my J7 is sluggish, so I wonder why would it have 4 processors idling if they could work (assuming the causes are processing several apps, which could be tackled by assigning different processors).

There are apps that can accomplish this task (e.g. "Kernel Adiutor" and others), however they in turn require other apps that can grant them root access to begin with, which is a lot of modification for this simple task. In any regular Linux desktop system, setting the governor at every boot would be accomplished by creating a script, for example in rc.local or a systemd-oneshot, that simply calls echo "" > /sys/devices/system/cpu/cpu*/cpufreq/scaling_governor after each system start. What would be the Android equivalent of this solution? Is there any way to automatically set the CPU governor without installing any apps?