I would like to know what sets the ro.hardware property. I cant seem to find in the build property files on the device. Is it set in the BoardConfig.mk or device.mk file when building android

I am trying to turn an old Samsung Galaxy S8 into a TV box. I want TV apps to be available in Google Play (like YouTube TV), but they are still showing as unsupported even after changing build.prop. I copied these fields from the Nvidia Shield TV build.prop: - ro.product.model - ro.product.brand - ro.product.name - ro.product.device - ro.product.manufacturer - ro.build.fingerprint - ro.build.characteristics=tv I cleared Google Play's data and rebooted the phone, but YouTube TV is still shown as unsupported.

There are many build.prop tweaks on the internet, and some says dalvik.vm.execution-mode should be int:jit, and some says it should be fast:jit or even in a reversed order as jit:fast for performance. What is the difference between int and fast, and does the order matter (before and after the colon)? My phone is running Android 4.4.2 KitKat. Edit: Just a note, ART is not supported in my device (Samsung Galaxy Note 2), even if I install the dex2oat program and libart.so, it won't work.

The Android device identifies itself as "device" for ADB (Android Debug Bridge). $ adb devices List of devices attached 5727aa6d device In my case of the LineageOS 20.0 test build, the name contains whitespaces and therefore cannot be addressed from [scrcpy](https://github.com/Genymobile/scrcpy/issues/3545) . $ adb devices List of devices attached CDC ACM Data device Which property can we set to change the adb device name?

I need to know the *CID* of an HTC 10 but,

adb shell getprop ro.cid

is unresponsive. Also

$ fastboot devices
FA**********	 fastboot
$ fastboot oem readcid
FAILED (remote: 'unknown command')
fastboot: error: Command failed

Also, grep -ril cid is unsuccessful on root. How can I get the *CID* info on my Android device?

I have a Samsung Galaxy S20 FE 5G. I'm using [Android System Info](https://play.google.com/store/apps/details?id=com.arumcomm.systeminfo) app to see how the system is running, and in the app, I see that I don't have HW and VM security policy. It's written security.securehw.available(false) and security.securevm.avaiable(false), and I also have ro.build.keys(test key). I think this configuration is not normal and the phone has been modified Is it normal?

I soft-bricked my Huawei G700 running Android 4.2.1 by editing a line in build.prop, specifically this one. ro.config.hwtheme=1 to ro.config.hwtheme=0 My phone didn't like that apparently. It supposedly fixes the Xposed framework limited mode bug. Now, I can boot into recovery and restore my phone to factory reset, but this is not something I'm very willing to do unless everything else fails. In recovery, I'm unable to use ADB to connect to my phone, I can wipe things, reset and apply patches, but that's it. Now, if I boot my phone and it gets stuck in the boot animation, I can suddenly use adb fine. Hurray right? Just restore build.prop.bak. Yeah, not. Nothing works.

chmod 777 build.prop -> Read-only
su chmod 777 build.prop -> nothing happens
su mv build.prop build.prop.back -> nothing happens
su -> nothing happens
su -s -> chainfire information ( from SuperSU )
mount -o remount,rw /system /system -> not permitted
su mount -o remount,rw /system /system -> nothing happens

All these commands were run in /system Can someone help me out with this? I don't want to have to use my last resort. **So, what's changed?** Well, if I boot normally, the phone functions fine in the background as if I didn't enter a PIN code. It requests an IP address from my router and connects fine, but something like web.whatsapp.com won't work. Volume Down + Power boots into... Fastboot? Well, kinda, not really. It just says two things

NEW:RISK
OLD:RISK

What I found on Google isn't much and it isn't promising. No solutions. When I boot the device, fastboot does detect the device as an mt6589 with the boot image being secure. SPFlasher does not work, it fails to detect my device in any mode and will not flash anything. I tried updating from recovery with a zip file but everything fails. After some googling, it appears to be likely that the zip file has to be signed by Huawei themselves. I tried installing adbd insecure v2 from Chainfire, but I have NO idea how to enable this from adb. I can't enable this the normal way. So, here's what I thought. Can't I call the Huawei theme *manually* from the adb shell? For that, I need someone else who can check this. If that doesn't work, do you guys have any other ideas? If none of those work, I could ask for an OEM key and flash another recovery, but that seems like a terrible idea as I have no GUI. Then there are three things left, sending it to Huawei / dropping it at a local repair shack, neither appeals as they are costly and mean I'll lose my phone for a while. Or, and that's the thing I really don't want to, buy another phone. I'm content with the phone itself, curiosity merely killed it. **I think I can't edit it because it's in use, not because I lack access as can be seen here ** Cheered too early.

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?

I have a stock + rooted Nexus 6 on Android 6.0.1. The editor I was using bugged out and wiped my build.prop file. I haven't rebooted yet, so the phone is still fine able to do things. There is no backup of the file. What are my options here? Is there an easy way to fix this?

I have a TCL 20e (6125A) with Android 11. I want to increase the torch brightness. As I read in another post, this can be done by adding these two lines in the file:

ro.media.capture.flashintensity=50
ro.media.capture.torchintensity=50

I look everywhere and can't root my device, and the two custom recoveries that I find don't work on my phone. Is it possible to edit this file without custom recovery? Any other chance?

I want to use an application for mobile devices on my android box. I am using X96 Max+, and when I install an app, the version for android tv-s gets installed, and I want to have a version for android phone devices. If I directly download the version for mobile devices, the warning goes off and says "This application can't be used on a non-mobile device!". Box uses android version 9, so I tried to edit build.prop file (the device is rooted), and set ro.product.brand and ro.product.model to google pixel 2 I think. And nothing happens. If I go in setting and about, I can see that these properties have been changed. So my question is, how can I know which parameters the app inspects before installation/launch and how to find what to edit to make it work.

This is MXQ Pro 4k box on Amlogic S905 chip. It is embarrassingly quiet when playing through the AV jack with some good active speakers attached. My Ubuntu laptop is able to play loud on those speakers. The MXQ Box itself is able to play loud via the HDMI when connected to a regular TV. I suspect Android thinks it's headphones attached to the AV jack and halves the volume to save my ears. But actually it's good speakers and I want it loud. Volume boost programs don't work. One of them - "Volume Booster GOODEV" - splashed a baloon saying something like "Loudness Enhancer Effect" is unavailable to the app. So I went redeye and started exploring the files on the device. /system/etc/audio_effects.conf mentions the loudness enhancer twice, the .so file is in place at the path mentioned, looks ok to my ignorant view: libraries: { ...... loudness_enhancer { path /system/lib/soundfx/libldnhncr.so } } ..... effects: { loudness_enhancer { library loudness_enhancer uuid fa415329-2034-4bea-b5dc-5b381c8d1e2c } } So I thought I am unable to give the Goodev app and plethora of other equalizers access to the effects, and started to dig more. I somehow managed to add "volume steps" in the build.prop: ro.config.media_vol_steps=16 unfortunately that didn't make the speakers any louder. Is there a ro.config.media_vol_max_db anywhere? How do people know what magic letters to spell in the config?... Okay, then I've googled about the mixer_paths.xml that allows people to boost the voulmes of their phones from some default 84 mystery units to 100... unfortunately, this is how my mixer_paths.xml file looks like: Question: **what should I try next?** The firmware looks a little like this if you want to really dig in https://mega.nz/file/l1x0GLDY#p3hs8aZxIAMM5LwIOtfpyis_w7C7XPQgYYBevGxkAmc the board looks like this **Add:** There are some ALSA artifacts in the filesystem, too: /usr/share/alsa/alsa.conf and ../pcm/default.conf

Can someone please explain in detail about different properties in build.prop file present in Android OS? Location of file: /system/build.prop

I have a nexus 6 with version 6.0.1 of android flashed and rooted using Nexus Root toolkit 2.1.4. I am trying to modify build.prop and doing adb pull/push and even trying to move it to /data/local/tmp and then mv command won't work. Mounting /system/ rw results in a boot loop and I have to reflash. I am unsure on how to enable modification of this file. How can I turn off this "production build" protection on android? adb shell shell@shamu:/ $ su root@shamu:/ # mv /data/local/tmp/build.prop /system/ mv: /system//build.prop: Read-only file system 1|root@shamu:/ # mount -o rw,remount /system 127|root@shamu:/ # mv /data/local/tmp/build.prop /system/ mv: xwrite: No space left on device 1|root@shamu:/ # exit 1|shell@shamu:/ $ exit adb push build.prop /system/build.prop failed to copy 'build.prop' to '/system/build.prop': Permission denied adb shell shell@shamu:/ $ su root@shamu:/ # mv /data/build.prop /sy sys/ system/ root@shamu:/ # mv /data/build.prop /system/build.prop mv: /system/build.prop: Read-only file system I'm trying to add this config option to build.prop net.tethering.noprovisioning=true The device has plenty of space as it was just freshly rooted and flashed with a brand new stock image.

I have tried to edit build.prop for on screen navigation keys, but, unexpectedly get cleared build.prop file and got saved. What can be done to regenerate file? Should reinstall zip should solve it? Or can I copy file(build.prop) by extracting from ROM zip.