Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Redmi Note 9T 5G (cannon/cannong) In-Call volume not adjustable #1908

Closed
dsclee1 opened this issue Jun 18, 2021 · 29 comments
Closed

Redmi Note 9T 5G (cannon/cannong) In-Call volume not adjustable #1908

dsclee1 opened this issue Jun 18, 2021 · 29 comments

Comments

@dsclee1
Copy link

dsclee1 commented Jun 18, 2021

I can't adjust the in-call volume on my device. Logcat suggests the button press is being recognised (and the change displays on the slider on screen), but there's no effect on the volume. Full Logcat is attached. Here's an example of a relevant section after a volume button press:
logcat.txt

06-18 14:27:53.461  1722  3794 D MediaSessionService: Adjusting com.android.server.telecom/HeadsetMediaButton (userId=0) by -1. flags=4113, suggestedStream=-2147483648, preferSuggestedStream=false
06-18 14:27:53.464  1722  3794 D MediaSessionService: dispatchVolumeKeyEvent, pkg=com.google.android.dialer, opPkg=com.google.android.dialer, pid=10813, uid=10151, asSystem=true, event=KeyEvent { action=ACTION_UP, keyCode=KEYCODE_VOLUME_DOWN, scanCode=114, metaState=0, flags=0x8, repeatCount=0, eventTime=6518763, downTime=6518636, deviceId=2, source=0x101, displayId=-1 }, stream=-2147483648, musicOnly=false
06-18 14:27:53.464  1722  3794 D MediaSessionService: Adjusting com.android.server.telecom/HeadsetMediaButton (userId=0) by 0. flags=4116, suggestedStream=-2147483648, preferSuggestedStream=false
06-18 14:27:53.474  1017  1197 I hwcomposer: [DPY] receive refesh frquest from driver: type[4]
06-18 14:27:53.474  1017  1197 I hwcomposer: [HWC] fire a callback of refresh to SF
06-18 14:27:53.476  1937  2237 I vol.Events: writeEvent level_changed STREAM_VOICE_CALL 3
06-18 14:27:53.480  1610  1620 D AudioALSAHardware: setVoiceVolume(), volume = 0.600000, mUseTuningVolume = 0
06-18 14:27:53.480  1610  1620 D AudioALSAStreamManager: setVoiceVolume(), volume = 0.600000
06-18 14:27:53.480  1610  1620 D AudioMTKGainController: setVoiceVolume(), index = 4, devices = 0x1, mode = 2, mBand = 1, mNetwork = 0, mVoiceVolume = 0.600000
06-18 14:27:53.480  1610  1620 D SpeechDriverOpenDSP: SetDownlinkGain(), gain = 0x0, old mDownlinkGain = 0x0
06-18 14:27:53.481  1610  1620 D AudioMTKGainController: ApplyMicGain(), analogidx = 2, mSceneIndex = 0, _mic_mode = 1, _gain_device = 0, mode = 2, micgain = 23, mULTotalGain = 164, mBand = 1, mNetwork = 0
06-18 14:27:53.481  1610  1620 E AudioMTKGainController: SetAdcPga3(), Error: get mixer ctl fail,
06-18 14:27:53.481  1610  1620 D SpeechDriverOpenDSP: SetUplinkGain(), gain = 0x3c, old mUplinkGain = 0x3c
06-18 14:27:53.481  1610  1620 D AudioMTKGainController: GetSPKGain
06-18 14:27:53.481  1610  1620 D AudioMTKGainController: GetSPKGain i = 0 index = 31
06-18 14:27:53.481  1610  1620 D AudioMTKGainController: updateSidetone(), DSP_ST_GAIN = 0, positive_gain_db = 0, dlPGAGain 0, sidetone 0, ulGain 15
06-18 14:27:53.481  1610  1620 D AudioMTKGainController: ApplySideTone gainDevice 0, sidetone 0, updated_sidetone 0
06-18 14:27:53.490  1937  2237 I vol.Events: writeEvent key STREAM_VOICE_CALL 3
06-18 14:27:53.500  1937  1937 I vol.Events: writeEvent show_dialog volume_changed keyguard=false

I'm also having an issue with headphones not being recognised by the audio jack, which could be related as it's tied in to the audio system, but the in-call volume problem is more of an issue right now.

I've already set "Bluetooth workarounds" to "Mediatek" and "Force-disable A2DP offload" to "on". This fixed bluetooth audio output, but not the in-call volume issue.

So far I've tried copying over the audio_policy files from the stock system image, but could see no change in my issue.
@phhusson
Copy link
Owner

phhusson commented Jun 18, 2021 via email

@dsclee1
Copy link
Author

dsclee1 commented Jun 20, 2021

I'm a bit reluctant to go back to the stock rom at the moment as there's not currently a custom recovery for this phone that will do a full backup.

I'll ask on the XDA forum to see if anyone can provide a stock logcat with in-call volume adjustments. If not I'll do it myself tomorrow.

@phhusson
Copy link
Owner

phhusson commented Jun 20, 2021 via email

@dsclee1
Copy link
Author

dsclee1 commented Jun 22, 2021

I've gone ahead and done it myself. Please see logcat attached.

The "KeyEvents" show where I've done the volume button presses. e.g.

06-22 10:08:32.634 14014 14014 D MIUIInput: [KeyEvent] ViewRootImpl KeyEvent { action=ACTION_UP, keyCode=KEYCODE_VOLUME_UP, scanCode=115, metaState=0, flags=0x8, repeatCount=0, eventTime=481361, downTime=481216, deviceId=2, source=0x101, displayId=-1 }
MIUI 12.5 in call volume logcat.txt

@dsclee1
Copy link
Author

dsclee1 commented Jun 22, 2021

Just to add, my headphones issue was solved by turning on "Use alternate way to detect headsets".

The in-call volume is still an issue though.

@phhusson
Copy link
Owner

I guess the trick is in
06-22 10:08:32.664 607 3527 D AudioALSAStreamOut: +setParameters(): flag 2, volumeDevice=1;volumeIndex=3;volumeStreamType=0

I'll dig with that. Thanks.

@dsclee1
Copy link
Author

dsclee1 commented Jun 23, 2021

Thanks.

I was wondering if it's something to do with the "mBand" setting?

On the stock rom it's:
06-22 10:08:33.462 607 3527 D AudioMTKGainController: setVoiceVolume(), index = 4, devices = 0x1, mode = 2, **mBand = 0**, mNetwork = 0, mVoiceVolume = 1.000000

and on the custom rom it's:
06-18 14:27:53.480 1610 1620 D AudioMTKGainController: setVoiceVolume(), index = 4, devices = 0x1, mode = 2, **mBand = 1**, mNetwork = 0, mVoiceVolume = 0.600000

I had a browse around some code on GitHub (https://github.com/iykex/vendor_mediatek_proprietary_hardware/blob/a592a52719cb43d2364e9c4d641f68ff6442d959/audio/common/V3/aud_drv/AudioALSAGainController.cpp and https://github.com/PixelExperience/vendor_mediatek-opensource/blob/eleven/external/audio_utils/common_headers/gain_table/AudioGainTableParam.h), and it looks like the stock rom sets it to GAIN_SPEECH_NB and the custom rom sets it to GAIN_SPEECH_WB. I have no idea what this actually means in practice though? I couldn't find info on what the "band" means in this context.

@dsclee1
Copy link
Author

dsclee1 commented Jun 23, 2021

I've done a bit more digging. GAIN_SPEECH_NB means Narrow Band and GAIN_SPEECH_WB means Wideband, which from what I gather Wideband is VoLTE. I had a go at enabling VoLTE via the "IMS Features" to see if that would help, but I've turned on what it would let me, and "Install IMS APK" says "NOT SUPPORTED", so that idea is out.

I think what's happening is that the custom rom is assuming the call is in VoLTE mode, and attempting to change the volume for a VoLTE call, but in reality the call is running in standard narrow band mode, so the volume change isn't being applied - but I might still be completely wrong!

@dsclee1
Copy link
Author

dsclee1 commented Jun 24, 2021

I tried turning off VoLTE using any VoLTE setting from getprop:
[persist.dbg.volte_avail_ovr]: [0]
[persist.vendor.mtk.volte.enable]: [0]
[persist.vendor.mtk_ct_volte_support]: [0]
[persist.vendor.mtk_hvolte_indicator]: [0]
[persist.vendor.volte_support]: [0]

I'm still seeing mBand = 1 in logcat when trying an in-call volume change:
06-24 08:19:49.604 1617 1885 D AudioMTKGainController: setVoiceVolume(), index = 4, devices = 0x1, mode = 2, mBand = 1, mNetwork = 0, mVoiceVolume = 0.600000

@phhusson
Copy link
Owner

Before going into side-effect stuff, you first need to look at first-effects -_-'

The line I quoted 06-22 10:08:32.664 607 3527 D AudioALSAStreamOut: +setParameters(): flag 2, volumeDevice=1;volumeIndex=3;volumeStreamType=0 exists in your stock rom, but NOT in AOSP. This is a command sent from framework to vendor, and it is NOT sent in AOSP.

So yeah if the command to set volume is not set, volume won't be set. No need to look into VoLTE for that

@lapingv755
Copy link

I have attached my logcats.
My device is a Blackview BV9500 Plus (MediaTek Helio P70) and i cannot adjust the in call volume as well.
In my case the volume is on max on all of the following: headset, headphones, loudspeaker.
I have not tried bt, so i cannot comment on that.

I am not sure if it's the same issue as my logcat looks a bit different
stock:
AudioMTKGainController: setVoiceVolume(), index = 1, devices = 0x1, mode = 2, mBand = 1, mNetwork = 0, mVoiceVolume = 1.000000

gsi:
AudioMTKGainController: setNormalVolume(), mSceneIndex = 0, stream -1, devices 0x1, index -1, mode 0x0
AudioMTKGainController: error, stream -1 is invalid, use 3 instead
AudioMTKGainController: error, index -1 is invalid, use max 15 instead

Both logs are somewhat old, but i can get new ones alongside anything else you need.
stock.txt
new_logcat.txt

@dsclee1
Copy link
Author

dsclee1 commented Jul 1, 2021

Before going into side-effect stuff, you first need to look at first-effects -_-'

The line I quoted 06-22 10:08:32.664 607 3527 D AudioALSAStreamOut: +setParameters(): flag 2, volumeDevice=1;volumeIndex=3;volumeStreamType=0 exists in your stock rom, but NOT in AOSP. This is a command sent from framework to vendor, and it is NOT sent in AOSP.

So yeah if the command to set volume is not set, volume won't be set. No need to look into VoLTE for that

Point taken! I've downloaded the source tree using the build.sh. I've run a search for "AudioALSAStreamOut", "AudioMTKGainController", and "AudioALSAHardware". But found no results. I can see results for the "setVoiceVolume" function, but these tie up to "AudioFlinger".

Am I even looking in the right place?

@phhusson
Copy link
Owner

Yes. That's precisely the issue. volumeDevice/volumeIndex commands are proprietary mediatek, and need to be added for this to work.

@eremitein
Copy link

eremitein commented Jul 17, 2021 •
edited
Loading

AudioALSAStreamOut

there is some code on the Github
https://github.com/search?q=AudioALSAStreamOut&type=code

@Vgdn1942
Copy link

Vgdn1942 commented Jul 19, 2021 •
edited
Loading

Yes. That's precisely the issue. volumeDevice/volumeIndex commands are proprietary mediatek, and need to be added for this to work.

I can provide ALPS android 9.0 source codes (t-alps-release-p0.mp1-V5.75.mt6750) if it can help. I do not yet have enough knowledge to deal with this problem alone.

@dsclee1
Copy link
Author

dsclee1 commented Jul 19, 2021

I've had a look at the sound controller down at the device level. If I run the following command as su during a call (using tinymix) I can reduce the in-call volume (CANNONG specific):
tinymix 390 16

This sets "Handset Volume" to 16. The number needs to be between 0 and 18, and then 31 is mute. 0 is loud, 18 is quiet (I.E. the higher the number the quieter it is).

Mileage will vary depending on your device. You probably won't be lucky enough that "Handset Volume" is item 390 in tinymix for other devices, so you'll need to run tinymix yourselves and find out which number "Handset Volume" is registered under. Something like this should help:
tinymix | grep 'Handset Volume'

@phhusson I don't know the feasibility of implementing this somehow as a framework code patch? It would obviously be very hacky.

@phhusson
Copy link
Owner

phhusson commented Jul 19, 2021 via email

@xenon205
Copy link

But I don't want that in my GSI, since I'm expecting that the audio system parameters I've given earlier are enough to set volume

That's good to hear. We will wait for Your implementation. Thank You

@phhusson
Copy link
Owner

phhusson commented Jul 19, 2021 via email

@xenon205
Copy link

Fair enough maybe some one else will be able to pick up gloves :)

@dsclee1
Copy link
Author

dsclee1 commented Jul 20, 2021 •
edited
Loading

As a short term solution, I've hacked together a script which can be used in Magisk (create it in /data/adb/service.d/).

#!/bin/sh
while [ "$(getprop sys.boot_completed | tr -d '\r')" != "1" ]; do sleep 1; done
sleep 1
# audio system min volume
inmin=$(/system/bin/service call audio 17 i32 0 | /system/bin/awk -F ' ' '{print $3}')
# audio system max volume
inmax=$(/system/bin/service call audio 18 i32 0 | /system/bin/awk -F ' ' '{print $3}')
# output max volume (lowest number)
outmax=$(/system/bin/tinymix "Handset Volume" | /system/bin/awk -F ' ' '{print $5}' | /system/bin/awk -F '-' '{print $1}')
# output min volume (highest number)
outmin=$(/system/bin/tinymix "Handset Volume" | /system/bin/awk -F ' ' '{print $5}' | /system/bin/awk -F '>' '{print substr($2,1,length($2)-1)}')
# calculate intervals (ceiling)
interval=$(/system/bin/expr $(/system/bin/expr $outmin + $inmax - 1) / $inmax)
# starting volume for audio system
incurrentold=$(/system/bin/service call audio 16 i32 0 | /system/bin/awk -F ' ' '{print $3}') 
# starting volume for hardware
outcurrent=$(/system/bin/tinymix "Handset Volume" --v)
outcurrentold=99
/system/bin/log -t MTKInCallDirtyFix "AudioManager Min Volume: $inmin"
/system/bin/log -t MTKInCallDirtyFix "AudioManager Max Volume: $inmax"
/system/bin/log -t MTKInCallDirtyFix "AudioManager Current Volume: $incurrentold"
/system/bin/log -t MTKInCallDirtyFix "Hardware Min Volume: $outmin"
/system/bin/log -t MTKInCallDirtyFix "Hardware Max Volume: $outmax"
/system/bin/log -t MTKInCallDirtyFix "Hardware Current Volume: $outcurrent"
/system/bin/log -t MTKInCallDirtyFix "Hardware Volume Interval: $interval"
/system/bin/log -t MTKInCallDirtyFix "Starting Service"
# loop
# run every 0.5 seconds
while true
do
  # check the handset is active
  outcurrent=$(/system/bin/tinymix "Handset Volume" --v)
  if [ "$outcurrent" -le "$outmin" ] && [ "$outcurrent" -ge "$outmax" ]
  then
    # get the audio system value and check that it's changed, or force it if it's the first entry to the call
    incurrent=$(/system/bin/service call audio 16 i32 0 | /system/bin/awk -F ' ' '{print $3}')
    if [ "$incurrentold" != "$incurrent" ] || [ "$outcurrentold" -gt "$outmin" ]
    then
      if [ "$incurrent" -ge "$inmax" ]
      then
        newhardwarevol=$outmax
      elif [ "$incurrent" -le "$inmin" ]
      then
        newhardwarevol=$outmin
      else
        # calculate the new hardware volume, by flipping the audio system volume round and multiplying by the interval
        flipvol=$(/system/bin/expr $inmax - $incurrent)
        newhardwarevol=$(/system/bin/expr $flipvol \* $interval)
      fi
      /system/bin/tinymix "Handset Volume" $newhardwarevol
      /system/bin/log -t MTKInCallDirtyFix "Hardware In-Call Volume: $newhardwarevol"
      incurrentold=$incurrent
    fi
  fi
  outcurrentold=$outcurrent
  sleep 0.5
done

It makes calls to the Audio service to work out Android's idea of what the volume should be, then calculates and applies it to the Hardware using tinymix. If anyone wants to try it out let me know how you get on.

@chaoscreater
Copy link

chaoscreater commented Nov 15, 2021 •
edited
Loading

#!/bin/sh
while [ "$(getprop sys.boot_completed | tr -d '\r')" != "1" ]; do sleep 1; done
sleep 1

audio system min volume

inmin=$(/system/bin/service call audio 17 i32 0 | /system/bin/awk -F ' ' '{print $3}')

audio system max volume

inmax=$(/system/bin/service call audio 18 i32 0 | /system/bin/awk -F ' ' '{print $3}')

output max volume (lowest number)

outmax=$(/system/bin/tinymix "Handset Volume" | /system/bin/awk -F ' ' '{print $5}' | /system/bin/awk -F '-' '{print $1}')

output min volume (highest number)

outmin=$(/system/bin/tinymix "Handset Volume" | /system/bin/awk -F ' ' '{print $5}' | /system/bin/awk -F '>' '{print substr($2,1,length($2)-1)}')

calculate intervals (ceiling)

interval=$(/system/bin/expr $(/system/bin/expr $outmin + $inmax - 1) / $inmax)

starting volume for audio system

incurrentold=$(/system/bin/service call audio 16 i32 0 | /system/bin/awk -F ' ' '{print $3}')

starting volume for hardware

outcurrent=$(/system/bin/tinymix "Handset Volume" --v)
outcurrentold=99
/system/bin/log -t MTKInCallDirtyFix "AudioManager Min Volume: $inmin"

Doesn't seem to work for me. I created a .sh file called "InCall_Volume.sh" and pasted your script into the file. Then I copied the file to /data/adb/service.d and restarted my phone. I don't see this in Magisk (probably because it's not a module), but I can see in Magisk logs it says "running service.d scripts". I made a test call and tried adjusting volume and it doesn't do anything...

but it could be because I'm using OctaviOS and not Lineage?

UPDATE:
Looks like OctaviOS doesn't have tinymix under /system/bin......I then copied tinymix and put it in /system/bin and gave it full permissions. Restarted phone and it's still the same issue....

If I run "tinymix 390 16" in Termux while in a call, it lowers my volume so it is definitely working. However, the script itself doesn't seem to work...

If I run the script in Termux, I get this:

line 42: syntax error near unexpected token 'elif'
elif [ "$incurrent" -le "$inmin" ]

UPDATE 2:
I'm now using Lineage and it still doesn't work for me. If I run it in Termux, it works, but it doesn't work if I put the script in service.d for Magisk......btw, have to run Termux as su first in order to run script.

UPDATE 3:
OK, I got it working now. Here's how I did it:

  • Download fDroid and install Termux. Don't install Termux from the Play Store (this one is outdated and unsupported).
  • In Termux, you should already be in the home directory by default. From there, create a .sh file using "nano whateverName.sh".
  • Copy and paste the contents of the script into the script and save it (CTRL+O).
  • Test it in Termux by running su, then run bash whateverName.sh. It should not throw any errors.
  • Use Root Explorer or another file explorer app and browse to /data/data/com.termux/files/home and you should find your whateverName.sh script there. Copy this to /data/adb/service.d.
  • Give full execute permissions to your script (long tap the file and click Permissions if you're using Root Explorer).
  • Restart phone and check Magisk log. It should show "Running service.d scripts" and immediately after that, it should show "service.d: exec [whateverName.sh]".

I don't know why, but if I copy the script from my PC to my microSD card and then from there, copy it to service.d, it won't work. I have to edit the script in Termux first.

Also, you may need to put in "sleep 10" (without quotations) in the 2nd line of the script. I read somewhere that this is required, as the script may be executed too quickly during startup and not actually run or something like that.

Anyway, I just switched back to OctaviOS and did all the above and confirmed that the fix is working.

My only concern is, does this script create a wakelock or use up battery? If it needs to be running/monitoring in the background constantly, then I'm not sure how good this is for the battery. Having said that, I also don't understand the script and I'm not a programmer....

@dsclee1
Copy link
Author

dsclee1 commented Nov 15, 2021

Great to hear you got it working, and thanks for the tip on the "sleep 10".

I've had the script running on my phone for a few months now, and I haven't noticed any impact on the battery (I charge my phone each day, and after a full day of my use I still have over 70% battery left). I think most phones have a lot more running in the background anyway, so this script is pretty lightweight.

TTTT555 added a commit to TTTT555/device_xiaomi_begonia that referenced this issue Jan 9, 2022
@TTTT555
begonia: Fix in-call volumes
135f712 
 * add shell daemon for correcting volumes using tinymix (don't forget add this tool to build)
 * kang idea by phhusson/treble_experimentations#1908
TTTT555 added a commit to TTTT555/device_xiaomi_begonia that referenced this issue Jan 9, 2022
@TTTT555
begonia: Fix in-call volumes
f3001b3 
 * add shell daemon for correcting volumes using tinymix (don't forget add this tool to build)
 * kang idea by phhusson/treble_experimentations#1908
TTTT555 added a commit to TTTT555/device_xiaomi_begonia that referenced this issue Jan 9, 2022
@TTTT555
begonia: Fix in-call volumes
cf3ff60 
 * add shell daemon for correcting volumes using tinymix (don't forget add this tool to build)
 * kang idea by phhusson/treble_experimentations#1908
TTTT555 added a commit to TTTT555/device_xiaomi_begonia that referenced this issue Jan 9, 2022
@TTTT555
begonia: Fix in-call volumes
10a8ff4 
 * add shell daemon for correcting volumes using tinymix (don't forget add this tool to build)
 * kang idea by phhusson/treble_experimentations#1908
TTTT555 added a commit to TTTT555/device_xiaomi_begonia that referenced this issue Jan 9, 2022
@TTTT555
begonia: Fix in-call volumes
4c4bd41 
 * add shell daemon for correcting volumes using tinymix (don't forget add this tool to build)
 * kang idea by phhusson/treble_experimentations#1908
TTTT555 added a commit to TTTT555/device_xiaomi_begonia that referenced this issue Jan 9, 2022
@TTTT555
begonia: Fix in-call volumes
9d7f6f2 
 * add shell daemon for correcting volumes using tinymix (don't forget add this tool to build)
 * kang idea by phhusson/treble_experimentations#1908
Mashopy pushed a commit to PotatoDevices/device_xiaomi_begonia-old that referenced this issue Jan 11, 2022
@TTTT555 @Mashopy
begonia: Fix in-call volumes
64cc8c7 
* add shell daemon for correcting volumes using tinymix (don't forget add this tool to build)
* kang idea by phhusson/treble_experimentations#1908

Change-Id: I0599b27c0d742c06d0b6ee15014f5063a61100d4
7Soldier pushed a commit to begonia-lineage/android_device_xiaomi_begonia that referenced this issue May 29, 2022
@TTTT555 @7Soldier
begonia: rootdir: Fix in-call volumes
415f3c9 
* add shell daemon for correcting volumes using tinymix (don't forget add this tool to build)
* kang idea by phhusson/treble_experimentations#1908
* also adapt channels and sh path for A12

Signed-off-by: 7Soldier <reg.fm4@gmail.com>
7Soldier pushed a commit to begonia-lineage/android_device_xiaomi_begonia that referenced this issue Jun 11, 2022
@TTTT555 @7Soldier
begonia: rootdir: Fix in-call volumes
bade9f1 
* add shell daemon for correcting volumes using tinymix (don't forget add this tool to build)
* kang idea by phhusson/treble_experimentations#1908
* also adapt channels and sh path for A12

Signed-off-by: 7Soldier <reg.fm4@gmail.com>
7Soldier pushed a commit to begonia-lineage/android_device_xiaomi_begonia that referenced this issue Jun 11, 2022
@TTTT555 @7Soldier
begonia: rootdir: Fix in-call volumes
c71716b 
* add shell daemon for correcting volumes using tinymix (don't forget add this tool to build)
* kang idea by phhusson/treble_experimentations#1908
* also adapt channels and sh path for A12

Signed-off-by: 7Soldier <reg.fm4@gmail.com>
@LinkBoi00
Copy link

LinkBoi00 commented Jun 11, 2022 •
edited
Loading

I understand this is beyond the scope of treble but here is a simple audio parameters config fix which fixes in call volume adjustment for the earpiece. This is at least better than the bash scripts some people have been temporarily using hence why I am posting this here, just sharing knowledge.
https://gitlab.com/LinkBoi00/android_vendor_xiaomi_cannon/-/commit/4f353ba72199d20ba1fd21a45e1e4a1a4398145e

7Soldier pushed a commit to begonia-lineage/android_device_xiaomi_begonia that referenced this issue Jun 13, 2022
@TTTT555 @7Soldier
begonia: rootdir: Fix in-call volumes
b409367 
* add shell daemon for correcting volumes using tinymix (don't forget add this tool to build)
* kang idea by phhusson/treble_experimentations#1908
* also adapt channels and sh path for A12

Signed-off-by: 7Soldier <reg.fm4@gmail.com>
@dsclee1
Copy link
Author

dsclee1 commented Jun 13, 2022

I understand this is beyond the scope of treble but here is a simple audio parameters config fix which fixes in call volume adjustment for the earpiece. This is at least better than the bash scripts some people have been temporarily using hence why I am posting this here, just sharing knowledge. https://gitlab.com/LinkBoi00/android_vendor_xiaomi_cannon/-/commit/4f353ba72199d20ba1fd21a45e1e4a1a4398145e

This is a much better solution. Tested and confirmed working using Magisk (MTKInCallVolume.zip).

I'd be interested to know if this fixes the global Mediatek issue or just our Note9Ts?

7Soldier pushed a commit to begonia-lineage/android_device_xiaomi_begonia that referenced this issue Jun 14, 2022
@TTTT555 @7Soldier
begonia: rootdir: Fix in-call volumes
1610349 
* Add shell daemon for correcting volumes using tinymix (don't forget add this tool to build)
* Kang idea by phhusson/treble_experimentations#1908

* Refactored code
* Also adapt channels and sh path for A12

Signed-off-by: 7Soldier <reg.fm4@gmail.com>
7Soldier pushed a commit to begonia-lineage/android_device_xiaomi_begonia that referenced this issue Jun 16, 2022
@TTTT555 @7Soldier
begonia: rootdir: Fix in-call volumes
7d86292 
* Add shell daemon for correcting volumes using tinymix (don't forget add this tool to build)
* Kang idea by phhusson/treble_experimentations#1908

* Refactored code
* Also adapt channels and sh path for A12

Signed-off-by: 7Soldier <reg.fm4@gmail.com>
7Soldier pushed a commit to begonia-lineage/android_device_xiaomi_begonia that referenced this issue Jun 25, 2022
@TTTT555 @7Soldier
begonia: rootdir: Fix in-call volumes
979ebe5 
* Add shell daemon for correcting volumes using tinymix (don't forget add this tool to build)
* Kang idea by phhusson/treble_experimentations#1908

* Refactored code
* Also adapt channels and sh path for A12

Signed-off-by: 7Soldier <reg.fm4@gmail.com>
7Soldier pushed a commit to begonia-lineage/android_device_xiaomi_begonia that referenced this issue Jun 26, 2022
@TTTT555 @7Soldier
begonia: rootdir: Fix in-call volumes
97649e9 
* Add shell daemon for correcting volumes using tinymix (don't forget add this tool to build)
* Kang idea by phhusson/treble_experimentations#1908

* Refactored code
* Also adapt channels and sh path for A12

Signed-off-by: 7Soldier <reg.fm4@gmail.com>
7Soldier pushed a commit to begonia-lineage/android_device_xiaomi_begonia that referenced this issue Jun 26, 2022
@TTTT555 @7Soldier
begonia: rootdir: Fix in-call volumes
63dac9f 
* Add shell daemon for correcting volumes using tinymix (don't forget add this tool to build)
* Kang idea by phhusson/treble_experimentations#1908

* Refactored code
* Also adapt channels and sh path for A12

Signed-off-by: 7Soldier <reg.fm4@gmail.com>
7Soldier pushed a commit to begonia-lineage/android_device_xiaomi_begonia that referenced this issue Jul 1, 2022
@TTTT555 @7Soldier
begonia: rootdir: Fix in-call volumes
e5250b5 
* Add shell daemon for correcting volumes using tinymix (don't forget add this tool to build)
* Kang idea by phhusson/treble_experimentations#1908

* Refactored code
* Also adapt channels and sh path for A12

Signed-off-by: 7Soldier <reg.fm4@gmail.com>
7Soldier pushed a commit to begonia-lineage/android_device_xiaomi_begonia that referenced this issue Jul 10, 2022
@TTTT555 @7Soldier
begonia: rootdir: Fix in-call volumes
6508c5f 
* Add shell daemon for correcting volumes using tinymix (don't forget add this tool to build)
* Kang idea by phhusson/treble_experimentations#1908

* Refactored code
* Also adapt channels and sh path for A12

Signed-off-by: 7Soldier <reg.fm4@gmail.com>
7Soldier pushed a commit to begonia-lineage/android_device_xiaomi_begonia that referenced this issue Jul 12, 2022
@TTTT555 @7Soldier
begonia: rootdir: Fix in-call volumes
810b7ec 
* Add shell daemon for correcting volumes using tinymix (don't forget add this tool to build)
* Kang idea by phhusson/treble_experimentations#1908

* Refactored code
* Also adapt channels and sh path for A12

Signed-off-by: 7Soldier <reg.fm4@gmail.com>
7Soldier pushed a commit to begonia-lineage/android_device_xiaomi_begonia that referenced this issue Jul 13, 2022
@TTTT555 @7Soldier
begonia: rootdir: Fix in-call volumes
db2fd4e 
* Add shell daemon for correcting volumes using tinymix (don't forget add this tool to build)
* Kang idea by phhusson/treble_experimentations#1908

* Refactored code
* Also adapt channels and sh path for A12

Signed-off-by: 7Soldier <reg.fm4@gmail.com>
7Soldier pushed a commit to begonia-lineage/android_device_xiaomi_begonia that referenced this issue Jul 13, 2022
@TTTT555 @7Soldier
begonia: rootdir: Fix in-call volumes
86f7a7a 
* Add shell daemon for correcting volumes using tinymix (don't forget add this tool to build)
* Kang idea by phhusson/treble_experimentations#1908

* Refactored code
* Also adapt channels and sh path for A12

Signed-off-by: 7Soldier <reg.fm4@gmail.com>
7Soldier pushed a commit to begonia-lineage/android_device_xiaomi_begonia that referenced this issue Jul 13, 2022
@TTTT555 @7Soldier
begonia: rootdir: Fix in-call volumes
8a41cad 
* Add shell daemon for correcting volumes using tinymix (don't forget add this tool to build)
* Kang idea by phhusson/treble_experimentations#1908

* Refactored code
* Also adapt channels and sh path for A12

Signed-off-by: 7Soldier <reg.fm4@gmail.com>
7Soldier pushed a commit to begonia-lineage/android_device_xiaomi_begonia that referenced this issue Jul 14, 2022
@TTTT555 @7Soldier
begonia: rootdir: Fix in-call volumes
8396cca 
* Add shell daemon for correcting volumes using tinymix (don't forget add this tool to build)
* Kang idea by phhusson/treble_experimentations#1908

* Refactored code
* Also adapt channels and sh path for A12

Signed-off-by: 7Soldier <reg.fm4@gmail.com>
7Soldier pushed a commit to begonia-lineage/android_device_xiaomi_begonia that referenced this issue Jul 14, 2022
@TTTT555 @7Soldier
begonia: rootdir: Fix in-call volumes
f72e66a 
* Add shell daemon for correcting volumes using tinymix (don't forget add this tool to build)
* Kang idea by phhusson/treble_experimentations#1908

* Refactored code
* Also adapt channels and sh path for A12

Signed-off-by: 7Soldier <reg.fm4@gmail.com>
7Soldier pushed a commit to begonia-lineage/android_device_xiaomi_begonia that referenced this issue Jul 14, 2022
@TTTT555 @7Soldier
begonia: rootdir: Fix in-call volumes
dda5a3d 
* Add shell daemon for correcting volumes using tinymix (don't forget add this tool to build)
* Kang idea by phhusson/treble_experimentations#1908

* Refactored code
* Also adapt channels and sh path for A12

Signed-off-by: 7Soldier <reg.fm4@gmail.com>
7Soldier pushed a commit to begonia-lineage/android_device_xiaomi_begonia that referenced this issue Jul 15, 2022
@TTTT555 @7Soldier
begonia: rootdir: Fix in-call volumes
dce62af 
* Add shell daemon for correcting volumes using tinymix (don't forget add this tool to build)
* Kang idea by phhusson/treble_experimentations#1908

* Refactored code
* Also adapt channels and sh path for A12

Signed-off-by: 7Soldier <reg.fm4@gmail.com>
7Soldier pushed a commit to begonia-lineage/android_device_xiaomi_begonia that referenced this issue Jul 16, 2022
@TTTT555 @7Soldier
begonia: rootdir: Fix in-call volumes
388863d 
* Add shell daemon for correcting volumes using tinymix (don't forget add this tool to build)
* Kang idea by phhusson/treble_experimentations#1908

* Refactored code
* Also adapt channels and sh path for A12

Signed-off-by: 7Soldier <reg.fm4@gmail.com>
7Soldier pushed a commit to begonia-lineage/android_device_xiaomi_begonia that referenced this issue Jul 19, 2022
@TTTT555 @7Soldier
begonia: rootdir: Fix in-call volumes
07fe49f 
* Add shell daemon for correcting volumes using tinymix (don't forget add this tool to build)
* Kang idea by phhusson/treble_experimentations#1908

* Refactored code
* Also adapt channels and sh path for A12

Signed-off-by: 7Soldier <reg.fm4@gmail.com>
7Soldier pushed a commit to begonia-lineage/android_device_xiaomi_begonia that referenced this issue Jul 19, 2022
@TTTT555 @7Soldier
begonia: rootdir: Fix in-call volumes
9102e93 
* Add shell daemon for correcting volumes using tinymix (don't forget add this tool to build)
* Kang idea by phhusson/treble_experimentations#1908

* Refactored code
* Also adapt channels and sh path for A12

Signed-off-by: 7Soldier <reg.fm4@gmail.com>
7Soldier pushed a commit to begonia-lineage/android_device_xiaomi_begonia that referenced this issue Jul 19, 2022
@TTTT555 @7Soldier
begonia: rootdir: Fix in-call volumes
7c7c606 
* Add shell daemon for correcting volumes using tinymix (don't forget add this tool to build)
* Kang idea by phhusson/treble_experimentations#1908

* Refactored code
* Also adapt channels and sh path for A12

Signed-off-by: 7Soldier <reg.fm4@gmail.com>
7Soldier pushed a commit to begonia-lineage/android_device_xiaomi_begonia that referenced this issue Jul 19, 2022
@TTTT555 @7Soldier
begonia: rootdir: Fix in-call volumes
b40a9f1 
* Add shell daemon for correcting volumes using tinymix (don't forget add this tool to build)
* Kang idea by phhusson/treble_experimentations#1908

* Refactored code
* Also adapt channels and sh path for A12

Signed-off-by: 7Soldier <reg.fm4@gmail.com>
7Soldier pushed a commit to begonia-lineage/android_device_xiaomi_begonia that referenced this issue Jul 21, 2022
@TTTT555 @7Soldier
begonia: rootdir: Fix in-call volumes
315d011 
* Add shell daemon for correcting volumes using tinymix (don't forget add this tool to build)
* Kang idea by phhusson/treble_experimentations#1908

* Refactored code
* Also adapt channels and sh path for A12

Signed-off-by: 7Soldier <reg.fm4@gmail.com>
7Soldier pushed a commit to begonia-lineage/android_device_xiaomi_begonia that referenced this issue Jul 21, 2022
@TTTT555 @7Soldier
begonia: rootdir: Fix in-call volumes
e8fd925 
* Add shell daemon for correcting volumes using tinymix (don't forget add this tool to build)
* Kang idea by phhusson/treble_experimentations#1908

* Refactored code
* Also adapt channels and sh path for A12

Signed-off-by: 7Soldier <reg.fm4@gmail.com>
@dsclee1 dsclee1 closed this as completed Feb 28, 2023
@olsdf
Copy link

olsdf commented Aug 14, 2024

This method's does not work for me((

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
9 participants
@phhusson @dsclee1 @Vgdn1942 @eremitein @xenon205 @chaoscreater @lapingv755 @LinkBoi00 @olsdf