Android Volume Steps

android-volume-steps.md

Android Volume Steps

Warning

This is a rather old guide and may or may not work with modern versions of Android.

Connect through ADB

1. Boot into TWRP
2. Connect device to computer
3. Terminal: List devices with adb devices
4. TWRP: Mount > System

Get and edit props file

1. Terminal:

# Android <= 9
adb pull /system/build.prop

# Android 10 - 11
adb pull /system/default.prop

# Android >= 12
adb pull /default.prop

2. Editor: Add the following settings to the pulled file

ro.config.vc_call_vol_steps=14
ro.config.media_vol_steps=30

Push props file

1. Terminal: Push file back to the device

# Android <= 9
adb push build.prop /system/

# Android 10 - 11
adb push default.prop /system/

# Android >= 12
adb push default.prop /

2. Terminal: Adjust permissions of the pushed file

adb shell

# Android <= 9
cd /system
chmod 644 build.prop

# Android 10 - 11
cd /system
chmod 644 default.prop

# Android >= 12
cd /
chmod 644 default.prop

is this works for all android?

Not sure. You have to try.

Great. Thanks for the update! Cheers Richard

…

On Mon, 17 Jan 2022 at 07:22, ZhuohuiLi123 ***@***.***> wrote: ***@***.**** commented on this gist. ------------------------------ Just an update for Android 12. The default.prop is located at the root, so you don't need /system/ just type "adb pull default.prop "to pull the folder to your adb path location when you push, you have to type "adb push default.prop /", don't forget the "/" otherwise it will show something like "push require an argument" — Reply to this email directly, view it on GitHub <https://gist.github.com/1b5488921d6af22dfe02053739e43522#gistcomment-4031102>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AOU2RMTRKZJ3424VGNAQHPDUWO7R3ANCNFSM4K275E3Q> . Triage notifications on the go with GitHub Mobile for iOS <https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675> or Android <https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub>. You are receiving this because you were mentioned.Message ID: ***@***.***>

I want to try it, but is it safe?

I want to try it, but is it safe?

@masterewot I haven’t used this technique in quite a long time. So I can’t say if it’s safe to use or if it still works at all.

I want to try it, but is it safe?

@masterewot I haven’t used this technique in quite a long time. So I can’t say if it’s safe to use or if it still works at all.

I just tried it in my LG V20 H910 LineageOS 20, doesn't work at all, guess I will have to go back to magisk extensions.

@peace20021 There are some differences between Android versions regarding which file to edit. So I guess with newer versions that came out since I documented this “trick” things unfortunately changed again.

for chmod you need to run adb shell chmod
Maybe handy to point out

Thanks for sharing this. As a datapoint for others, the following worked for me on LineageOS 21 (a.k.a Android 14) on beckham, after enabling USB debugging and rooted debugging:

adb root

adb pull /system/build.prop

(make edits as described)

adb shell mount -o remount,rw /system

adb push build.prop /system

adb shell chmod 644 /system/build.prop

(reboot the device)