Database Info

Orbit 2 and Gear4 stereo bluetooth headset

Hi,
When I switch on both devices they connect fine, and I'm able to make calls etc, but the stereo connection doesn't appear to be established. I then have to go to Comm manager>Settings>Bluetooth, tap and hold my bluetooth headphone in the list, then choose 'Set as Wireless Stereo' from the list that appears.
As soon as I do this, the stereo connection is achieved and indicated by the headphone icon appearing in the top bar.
Is anybody else having this issue with stereo bluetooth headphones?
Is there a solution to this?

Aleemz,
I've just bumped in to this post - I have solved this on mine by writing a mortscript to automate the manual steps above.
It works pretty well, switching on the BT, waiting for the headset to connect, and then switching off the BT when the headset disconnects.
Here's the script (with thanks to another poster who gave me the starting block for this):
#power up bluetooth
Run ("\program files\vijay555\vjvolubilis\vjvolubilis.exe","-blueon")
#wait for something to connect, but only for 30 secs
SleepMessage( 30,"Connect Headset", "waiting for headset" , True ,RegRead("HKLM", "System\State\Hardware", "Handsfree") = 1 )
If (RegRead("HKLM", "System\State\Hardware", "Handsfree") = 0 )
#headset isn't connected, so switch off bt & give up
Run ("\program files\vijay555\vjvolubilis\vjvolubilis.exe","-blueoff")
exit
endif
#if we get here, then bt is on & the headset (or something) is connected
#may want to add logic here to decide what to do based on what device has connected
#run up the settings page
Run "\Program Files\MortScript\bluetoothcpl.lnk"
#wait for the settings page to load
WaitForActive ( "Settings",20 )
If (WndActive("Settings"))
#Great - it opened
#set the device
#may well have to add some logic here later to detect which BT device has connected
#This works if the BLuPhones are the 1st in the list
MouseDown Settings,60,125
Sleep 1000
MouseUp Settings,60,125
Sleep 500
SendDown
SendDown
SendDown
SendCR
Close "Settings"
#now we're all set up
#Now just wait for it to disconnect
#loop watching for bt headset disconnect for 4 hours, checking every minute
timcount = 0
while (timcount < 60*4)
timcount = timcount + 1
If (RegRead("HKLM", "System\State\Hardware", "Handsfree") = 0 )
#headset has dis-connected, so switch off bt & exit the apps
Call CloseAppsAndExit
Exit
endif
sleep 60000
EndWhile
#timeout after 4 hours of waiting, and shutdown media player & bt anyway
#do this in case it's been left on accidentally
Endif
Message("Closing down bluetooth now","Bye")
Call CloseAppsAndExit
Sleep 2000
Exit
Sub CloseAppsAndExit
#Close all apps we ran & exit
#close BT
Run ("\program files\vijay555\vjvolubilis\vjvolubilis.exe","-blueoff")
#close all apps -
Call ("CloseApp","GSPlayer")
Call ("CloseApp","Windows Media")
#this is the name of AVRCP I think
Call ("CloseApp","TCPMP")
Call ("CloseApp","S2P")
#and this is my guess at S2P
EndSub
Sub CloseApp
if (WndExists(argv[1]))
close(argv[1])
Endif
EndSub

Can someone post their audio.conf code

Can someone post their audio.conf code? It is locateed in /etc/bluetooth/
The reason I am asking this, is because I am trying to troubleshoot my bluetooth connectivity issues with my car radio. It supports 1.3 AVRCP yet I'm getting no meta-data. This is the code my phone is showing below. (Also, my playback pauses randomly)
Code:
# Configuration file for the audio service
# This section contains options which are not specific to any
# particular interface
# NOTE: Enable=Sink means that bluetoothd exposes Sink interface for remote
# devices, and the local device is a Source
[General]
Enable=Sink,Control
Disable=Headset,Gateway,Source
# request master role for incoming connections
# so as to reduce the number of piconets and
# allow lot more incoming connections
Master=false
# If we want to disable support for specific services
# Defaults to supporting all implemented services
#Disable=Control,Source
# SCO routing. Either PCM or HCI (in which case audio is routed to/from ALSA)
# Defaults to HCI
#SCORouting=PCM
# Automatically connect both A2DP and HFP/HSP profiles for incoming
# connections. Some headsets that support both profiles will only connect the
# other one automatically so the default setting of true is usually a good
# idea.
#AutoConnect=true
# Headset interface specific options (i.e. options which affect how the audio
# service interacts with remote headset devices)
#[Headset]
# Set to true to support HFP (in addition to HSP only which is the default)
# Defaults to false
#HFP=true
# Maximum number of connected HSP/HFP devices per adapter. Defaults to 1
#MaxConnections=1
# Set to true to enable use of fast connectable mode (faster page scanning)
# for HFP when incomming call starts. Default settings are restored after
# call is answered or rejected. Page scan interval is much shorter and page
# scan type changed to interlaced. Such allows faster connection initiated
# by a headset.
FastConnectable=false
# Just an example of potential config options for the other interfaces
[A2DP]
SBCSources=1
MPEG12Sources=0
[AVRCP]
InputDeviceName=AVRCP
MetaDataEnable=true
[WBspeech]
#for wide band speech hci commands arguments
WBSEnable = false
I2sEnable = 0x01
IsMaster = 0x00
ClockRate = 0x02
PcmInterfaceRate = 0x00
Any help with this is greatly appreciated.

197 Views and not one person willing to post? Just want to see the audio.conf from a person with working streaming meta data...

BungeBash said:
197 Views and not one person willing to post? Just want to see the audio.conf from a person with working streaming meta data...
Click to expand...
Click to collapse
Here you go
# Configuration file for the audio service
# This section contains options which are not specific to any
# particular interface
# NOTE: Enable=Sink means that bluetoothd exposes Sink interface for remote
# devices, and the local device is a Source
[General]
Enable=Sink,Control
Disable=Headset,Gateway,Source
# Switch to master role for incoming connections (defaults to true)
Master=false
# If we want to disable support for specific services
# Defaults to supporting all implemented services
#Disable=Control,Source
# SCO routing. Either PCM or HCI (in which case audio is routed to/from ALSA)
# Defaults to HCI
#SCORouting=PCM
# Automatically connect both A2DP and HFP/HSP profiles for incoming
# connections. Some headsets that support both profiles will only connect the
# other one automatically so the default setting of true is usually a good
# idea.
#AutoConnect=true
# Headset interface specific options (i.e. options which affect how the audio
# service interacts with remote headset devices)
#[Headset]
# Set to true to support HFP (in addition to HSP only which is the default)
# Defaults to false
#HFP=true
# Maximum number of connected HSP/HFP devices per adapter. Defaults to 1
#MaxConnections=1
# Set to true to enable use of fast connectable mode (faster page scanning)
# for HFP when incomming call starts. Default settings are restored after
# call is answered or rejected. Page scan interval is much shorter and page
# scan type changed to interlaced. Such allows faster connection initiated
# by a headset.
FastConnectable=false
# Just an example of potential config options for the other interfaces
[A2DP]
SBCSources=1
MPEG12Sources=0
[AVRCP]
InputDeviceName=AVRCP
# The Sony car stereo Ford is using under their brand as '6000 CD' has a
# completely broken AVRCP 1.3 implementation. After recognizing AVRCP 1.3 TG
# capabilities and exchanging a few PDUs, the car stereo disconnects and
# reconnects BT, also resetting USB devices if connected to it.
# To avoid that and allow at least HFP and A2DP to work, prevent any AVRCP 1.3
# PDUs from being sent on those models - add the device to the black list.
# Since 2012 Ford models have it fixed, removing the device from the list
# will result in full functionality.
MetaDataBlackList=Ford Audio
Sent from my SGS3 running Eclipse 2.1

I appreciate the response. I was hoping there was going to be more different than the little excerpt at the bottom :-/ Maybe it is just going to be an issue with uConnect in dodge cars. Unfortunately I have no other car to test with.

Bluetooth headset doesn't get call audio

Hi guys
I have an issue with my new bluetooth headset. I bought this Arctic P253BT headset to use on my Huawei Y300 (rooted with FusionX rom). It works properly on media stream. But when i start a call, despite i set bluetooth as output the audio comes out on phone speakers. Also headset integrated microphone doesn't work.
I tried the headset on iphone and it works properly. Then i tried on a Samsung Galaxy ace and it doesn't work at all.. all audio is on phone speakers. However... i didn't post this in the accessories forum because i think this is a software problem. I think that I need to change some settings to redirect call audio stream on bluetooth... so i need your nerd help
Noob's thanks
Update: I found out that the phone redirect correctly the bluetooth A2DP to headset, but the bluetooth mono stream is redirected on phone speakers... Can someone help?

Re-update:laugh:
This are the two files that i think should be important..
\system\etc\audio_policy.conf
#
# Audio policy configuration for generic device builds (goldfish audio HAL - emulator)
#
# Global configuration section: lists input and output devices always present on the device
# as well as the output device selected by default.
# Devices are designated by a string that corresponds to the enum in audio.h
global_configuration {
attached_output_devices AUDIO_DEVICE_OUT_SPEAKER|AUDIO_DEVICE_OUT_EARPIECE
default_output_device AUDIO_DEVICE_OUT_SPEAKER
attached_input_devices AUDIO_DEVICE_IN_BUILTIN_MIC|AUDIO_DEVICE_IN_VOICE_CALL
}
# audio hardware module section: contains descriptors for all audio hw modules present on the
# device. Each hw module node is named after the corresponding hw module library base name.
# For instance, "primary" corresponds to audio.primary.<device>.so.
# The "primary" module is mandatory and must include at least one output with
# AUDIO_OUTPUT_FLAG_PRIMARY flag.
# Each module descriptor contains one or more output profile descriptors and zero or more
# input profile descriptors. Each profile lists all the parameters supported by a given output
# or input stream category.
# The "channel_masks", "formats", "devices" and "flags" are specified using strings corresponding
# to enums in audio.h and audio_policy.h. They are concatenated by use of "|" without space or "\n".
#/* < DTS2012080708196 duhongyan 20120807 begin */
audio_hw_modules {
primary {
outputs {
primary {
sampling_rates 44100|48000
channel_masks AUDIO_CHANNEL_OUT_STEREO
formats AUDIO_FORMAT_PCM_16_BIT
devices AUDIO_DEVICE_OUT_SPEAKER|AUDIO_DEVICE_OUT_EARPIECE|AUDIO_DEVICE_OUT_WIRED_HEADSET|AUDIO_DEVICE_OUT_WIRED_HEADPHONE|AUDIO_DEVICE_OUT_ALL_SCO|AUDIO_DEVICE_OUT_AUX_DIGITAL|AUDIO_DEVICE_OUT_FM|AUDIO_DEVICE_OUT_FM_TX
flags AUDIO_OUTPUT_FLAG_PRIMARY
}
voipout {
sampling_rates 8000|16000
channel_masks AUDIO_CHANNEL_OUT_MONO
formats AUDIO_FORMAT_PCM_16_BIT|AUDIO_FORMAT_AMR_NB|AUDIO_FORMAT_AMR_WB|AUDIO_FORMAT_QCELP|AUDIO_FORMAT_EVRC|AUDIO_FORMAT_EVRCB|AUDIO_FORMAT_EVRCWB
devices AUDIO_DEVICE_OUT_EARPIECE|AUDIO_DEVICE_OUT_SPEAKER|AUDIO_DEVICE_OUT_WIRED_HEADSET|AUDIO_DEVICE_OUT_WIRED_HEADPHONE
flags AUDIO_OUTPUT_FLAG_DIRECT|AUDIO_OUTPUT_FLAG_VOIP_RX
}
lpa {
sampling_rates 8000|11025|12000|16000|22050|24000|32000|44100|48000
channel_masks AUDIO_CHANNEL_OUT_STEREO|AUDIO_CHANNEL_OUT_MONO
formats AUDIO_FORMAT_PCM_16_BIT
devices AUDIO_DEVICE_OUT_SPEAKER|AUDIO_DEVICE_OUT_EARPIECE|AUDIO_DEVICE_OUT_WIRED_HEADSET|AUDIO_DEVICE_OUT_WIRED_HEADPHONE|AUDIO_DEVICE_OUT_ALL_SCO|AUDIO_DEVICE_OUT_AUX_DIGITAL
flags AUDIO_OUTPUT_FLAG_DIRECT|AUDIO_OUTPUT_FLAG_LPA
}
}
inputs {
primary {
sampling_rates 8000|11025|12000|16000|22050|24000|32000|44100|48000
channel_masks AUDIO_CHANNEL_IN_MONO|AUDIO_CHANNEL_IN_STEREO|AUDIO_CHANNEL_IN_VOICE_CALL_MONO|AUDIO_CHANNEL_IN_VOICE_DNLINK_MONO|AUDIO_CHANNEL_IN_VOICE_UPLINK_MONO
formats AUDIO_FORMAT_PCM_16_BIT|AUDIO_FORMAT_AMR_NB|AUDIO_FORMAT_EVRC|AUDIO_FORMAT_QCELP
devices AUDIO_DEVICE_IN_BUILTIN_MIC|AUDIO_DEVICE_IN_WIRED_HEADSET|AUDIO_DEVICE_IN_BLUETOOTH_SCO_HEADSET|AUDIO_DEVICE_IN_AUX_DIGITAL|AUDIO_DEVICE_IN_VOICE_CALL|AUDIO_DEVICE_IN_FM_RX
}
voipin {
sampling_rates 8000|16000
channel_masks AUDIO_CHANNEL_IN_MONO
formats AUDIO_FORMAT_PCM_16_BIT|AUDIO_FORMAT_AMR_NB|AUDIO_FORMAT_AMR_WB|AUDIO_FORMAT_QCELP|AUDIO_FORMAT_EVRC|AUDIO_FORMAT_EVRCB|AUDIO_FORMAT_EVRCWB
devices AUDIO_DEVICE_IN_COMMUNICATION
}
}
}
a2dp {
outputs {
primary {
sampling_rates 48000
channel_masks AUDIO_CHANNEL_OUT_STEREO
formats AUDIO_FORMAT_PCM_16_BIT
devices AUDIO_DEVICE_OUT_ALL_A2DP
flags AUDIO_OUTPUT_FLAG_PRIMARY
}
}
}
}
#/* DTS2012080708196 duhongyan 20120807 end > */
\system\etc\bluetooth\audio.conf
# Configuration file for the audio service
# This section contains options which are not specific to any
# particular interface
# NOTE: Enable=Sink means that bluetoothd exposes Sink interface for remote
# devices, and the local device is a Source
[General]
Enable=Sink,Control
Disable=Headset,Gateway,Source
# request master role for incoming connections
# so as to reduce the number of piconets and
# allow lot more incoming connections
Master=true
# If we want to disable support for specific services
# Defaults to supporting all implemented services
#Disable=Control,Source
# SCO routing. Either PCM or HCI (in which case audio is routed to/from ALSA)
# Defaults to HCI
#SCORouting=PCM
# Automatically connect both A2DP and HFP/HSP profiles for incoming
# connections. Some headsets that support both profiles will only connect the
# other one automatically so the default setting of true is usually a good
# idea.
#AutoConnect=true
# Headset interface specific options (i.e. options which affect how the audio
# service interacts with remote headset devices)
#[Headset]
# Set to true to support HFP (in addition to HSP only which is the default)
# Defaults to false
#HFP=true
# Maximum number of connected HSP/HFP devices per adapter. Defaults to 1
#MaxConnections=1
# Set to true to enable use of fast connectable mode (faster page scanning)
# for HFP when incomming call starts. Default settings are restored after
# call is answered or rejected. Page scan interval is much shorter and page
# scan type changed to interlaced. Such allows faster connection initiated
# by a headset.
FastConnectable=false
# Just an example of potential config options for the other interfaces
[A2DP]
SBCSources=1
MPEG12Sources=0
[AVRCP]
InputDeviceName=AVRCP
Please someone help

I face the same problem (Y300, FusionX, Philips (mono) Headset).
There is a workaround, which is kind of annoying though : You can pair the bluetooth headset, then make a call. As usual, the call is still using the phone. If you switch to the bluetooth settings during the call and select your headset, it should show a "phone" profile with a checkbox. Disabling the checkbox and re-enabling it will correctly route the current call to your headset.
If anyone knows a real fix, I would be very happy to know and test it

[GUIDE] Fix imbalanced and/or quiet audio with the Apple USB-C headphone dongle

I have found a fix for the different channel volumes problem exhibited when using the Apple DAC dongle and the PH-1. This can also fix the quiet volume of this adapter.
Requirements:
Rooted PH-1 with Magisk
Tasker
Steps:
Follow _mysiak_'s tutorial to create a Magisk module for alsa. This module adds the command alsa_amixer which can level the two channels' volumes. Start with this template for a module. I had to rename the xbin folder to bin to get mine to work. If you want to skip learning about modules just grab mine here. Install the module within Magisk Manager.
In the Tasker shell script command put
Code:
alsa_amixer -c 1 sset PCM 120
And don't forget to set "run as root". This sets the level to max for TRS headphones, fixing the imbalance.
For TRRS (other headphones) do step 2 but with the following command
Code:
alsa_amixer -c 1 sset Headset,1 120
This fixes quiet audio for other headphones.
Big thanks to @_mysiak_ ! Would be nice if Essential could fix this the right way!

[Undervolt][Flashable] Oneplus 5T undervolt.

Steps:
1. Download https://github.com/lyq1996/msm8998_offset_voltage/releases/download/v1.0/msm8998-Undervolt-Tool.zip
2. Reboot to TWRP and select msm8999-Undervolt-Tool.zip
3. Enjoy.
Others:
1. How to check my current gpu and cpu voltage?
Open your terminal and run:
su -c dmesg -T | grep -E "add_opp|gfx3d_"
2. Most 835 can easily undervolt cpu 100mv and gpu 200mv!
3. Done in your own risks.

hello, wanted to check my stock voltage but your line gave me no results on the terminal, anything i am doing wrong? thanks

miky10 said:
hello, wanted to check my stock voltage but your line gave me no results on the terminal, anything i am doing wrong? thanks
Click to expand...
Click to collapse
Please reboot.
dmesg store in kernel ring buffer, it will replace old log when hit the buffer size.

Does this undervolt require a custom kernel?

[email protected] said:
Steps:
1. Download https://github.com/lyq1996/msm8998_offset_voltage/releases/download/v1.0/msm8998-Undervolt-Tool.zip
2. Reboot to TWRP and select msm8999-Undervolt-Tool.zip
3. Enjoy.
Others:
1. How to check my current gpu and cpu voltage?
Open your terminal and run:
su -c dmesg -T | grep -E "add_opp|gfx3d_"
2. Most 835 can easily undervolt cpu 100mv and gpu 200mv!
3. Done in your own risks.
Click to expand...
Click to collapse
just flashing is enough?
how to change the setting of undervolt (like -25,-50,-75...)

jraman said:
just flashing is enough?
how to change the setting of undervolt (like -25,-50,-75...)
Click to expand...
Click to collapse
via aroma

Will this work with blu_sprk? cause blu_sprk uses magisk to flash the kernel systemlessly

dsjd said:
Will this work with blu_sprk? cause blu_sprk uses magisk to flash the kernel systemlessly
Click to expand...
Click to collapse
It's not kernel.
Just a tool that undervolt by modify voltage_fuse in kernel_dtb.
So all roms and all recovery should work fine.

[email protected] said:
It's not kernel.
Just a tool that undervolt by modify voltage_fuse in kernel_dtb.
So all roms and all recovery should work fine.
Click to expand...
Click to collapse
Cool. What's the max that I can undervolt? Also at what stage of boot does the undervolt kick in?

:/ $ su -c dmesg -T | grep -E "add_opp|gfx3d_"
[Sat May 16 07:10:53 2020] gfx3d_clk_src: set OPP pair(180000000 Hz: 548000 uV) on 5000000.qcom,kgsl-3d0
[Sat May 16 07:10:53 2020] [ 0.410422]@4 gfx3d_clk_src: set OPP pair(710000000 Hz: 764000 uV) on 5000000.qcom,kgsl-3d0
[Sat May 16 07:10:53 2020] [ 0.435766]@4 add_opp: Set OPP pair (300000000 Hz, 568000 uv) on cpu0
[Sat May 16 07:10:53 2020] [ 0.436387]@4 add_opp: Set OPP pair (1900800000 Hz, 788000 uv) on cpu0
[Sat May 16 07:10:53 2020] [ 0.436414]@4 add_opp: Set OPP pair (300000000 Hz, 568000 uv) on cpu1
[Sat May 16 07:10:53 2020] [ 0.436794]@4 add_opp: Set OPP pair (1900800000 Hz, 788000 uv) on cpu1
[Sat May 16 07:10:53 2020] [ 0.436821]@4 add_opp: Set OPP pair (300000000 Hz, 568000 uv) on cpu2
[Sat May 16 07:10:53 2020] [ 0.437200]@4 add_opp: Set OPP pair (1900800000 Hz, 788000 uv) on cpu2
[Sat May 16 07:10:53 2020] [ 0.437229]@4 add_opp: Set OPP pair (300000000 Hz, 568000 uv) on cpu3
[Sat May 16 07:10:53 2020] [ 0.437611]@4 add_opp: Set OPP pair (1900800000 Hz, 788000 uv) on cpu3
[Sat May 16 07:10:53 2020] [ 0.437636]@4 add_opp: Set OPP pair (300000000 Hz, 568000 uv) on cpu4
[Sat May 16 07:10:53 2020] [ 0.438185]@4 add_opp: Set OPP pair (2457600000 Hz, 880000 uv) on cpu4
[Sat May 16 07:10:53 2020] [ 0.438211]@4 add_opp: Set OPP pair (300000000 Hz, 568000 uv) on cpu5
[Sat May 16 07:10:53 2020] [ 0.438758]@4 add_opp: Set OPP pair (2457600000 Hz, 880000 uv) on cpu5
[Sat May 16 07:10:53 2020] [ 0.438789]@4 add_opp: Set OPP pair (300000000 Hz, 568000 uv) on cpu6
[Sat May 16 07:10:53 2020] [ 0.439338]@4 add_opp: Set OPP pair (2457600000 Hz, 880000 uv) on cpu6
[Sat May 16 07:10:53 2020] [ 0.439367]@4 add_opp: Set OPP pair (300000000 Hz, 568000 uv) on cpu7
[Sat May 16 07:10:53 2020] [ 0.439914]@4 add_opp: Set OPP pair (2457600000 Hz, 880000 uv) on cpu7
[Sat May 16 07:10:53 2020] [ 0.749548]@4 iommu: Adding device 5040000.qcom,kgsl-iommu:gfx3d_user to group 11
[Sat May 16 07:10:53 2020] [ 0.749827]@4 iommu: Adding device 5040000.qcom,kgsl-iommu:gfx3d_secure to group 12
:/ $
Click to expand...
Click to collapse
Can someone tell me how to read this? As far as i understand, uV should be negative right?

:/ $ su
:/ # su -c dmesg -T | grep -E "add_opp|gfx3d_"
[Sat May 16 08:11:55 2020] gfx3d_clk_src: set OPP pair(180000000 Hz: 648000 uV) on 5000000.qcom,kgsl-3d0
[Sat May 16 08:11:55 2020] [ 0.422595]@4 gfx3d_clk_src: set OPP pair(710000000 Hz: 964000 uV) on 5000000.qcom,kgsl-3d0
[Sat May 16 08:11:55 2020] [ 0.447935]@4 add_opp: Set OPP pair (300000000 Hz, 660000 uv) on cpu0
[Sat May 16 08:11:55 2020] [ 0.448564]@4 add_opp: Set OPP pair (1900800000 Hz, 900000 uv) on cpu0
[Sat May 16 08:11:55 2020] [ 0.448592]@4 add_opp: Set OPP pair (300000000 Hz, 660000 uv) on cpu1
[Sat May 16 08:11:55 2020] [ 0.448980]@4 add_opp: Set OPP pair (1900800000 Hz, 900000 uv) on cpu1
[Sat May 16 08:11:55 2020] [ 0.449014]@4 add_opp: Set OPP pair (300000000 Hz, 660000 uv) on cpu2
[Sat May 16 08:11:55 2020] [ 0.449409]@4 add_opp: Set OPP pair (1900800000 Hz, 900000 uv) on cpu2
[Sat May 16 08:11:55 2020] [ 0.449439]@4 add_opp: Set OPP pair (300000000 Hz, 660000 uv) on cpu3
[Sat May 16 08:11:55 2020] [ 0.449838]@4 add_opp: Set OPP pair (1900800000 Hz, 900000 uv) on cpu3
[Sat May 16 08:11:55 2020] [ 0.449863]@4 add_opp: Set OPP pair (300000000 Hz, 644000 uv) on cpu4
[Sat May 16 08:11:55 2020] [ 0.450434]@4 add_opp: Set OPP pair (2457600000 Hz, 992000 uv) on cpu4
[Sat May 16 08:11:55 2020] [ 0.450463]@4 add_opp: Set OPP pair (300000000 Hz, 644000 uv) on cpu5
[Sat May 16 08:11:55 2020] [ 0.450995]@4 add_opp: Set OPP pair (2457600000 Hz, 992000 uv) on cpu5
[Sat May 16 08:11:55 2020] [ 0.451024]@4 add_opp: Set OPP pair (300000000 Hz, 644000 uv) on cpu6
[Sat May 16 08:11:55 2020] [ 0.451550]@4 add_opp: Set OPP pair (2457600000 Hz, 992000 uv) on cpu6
[Sat May 16 08:11:55 2020] [ 0.451578]@4 add_opp: Set OPP pair (300000000 Hz, 644000 uv) on cpu7
[Sat May 16 08:11:55 2020] [ 0.452104]@4 add_opp: Set OPP pair (2457600000 Hz, 992000 uv) on cpu7
[Sat May 16 08:11:55 2020] [ 0.760427]@4 iommu: Adding device 5040000.qcom,kgsl-iommu:gfx3d_user to group 11
[Sat May 16 08:11:55 2020] [ 0.760712]@4 iommu: Adding device 5040000.qcom,kgsl-iommu:gfx3d_secure to group 12
:/ #
Click to expand...
Click to collapse
If moderator think I'm spamming, feel free to remove it.
This is when i ran the command on stock. I saw difference with the clock speed, but i still don't understand about the uV value.

Will I still be able to use a mod like this if I'm on a custom ROM? Thanks!
(I'm very new to all this sorry)

yChoon said:
If moderator think I'm spamming, feel free to remove it.
This is when i ran the command on stock. I saw difference with the clock speed, but i still don't understand about the uV value.
Click to expand...
Click to collapse
1v = 1000mv = 1000000uv, logs the command output is your current big and small core voltage.
You can observe the changes before and after using the tool to determine whether undervolt is effective

Nafy77 said:
Will I still be able to use a mod like this if I'm on a custom ROM? Thanks!
(I'm very new to all this sorry)
Click to expand...
Click to collapse
Sure, work on all rom.

[email protected] said:
1v = 1000mv = 1000000uv, logs the command output is your current big and small core voltage.
You can observe the changes before and after using the tool to determine whether undervolt is effective
Click to expand...
Click to collapse
Thank you! But i already observe the effectiveness, my phone has lower temperature overall + battery lasting longer with 100mv uv on cpu and 200mv uv on gpu.
However, i would advice other those who about to use this mod, after flashing remember to use kernel manager to disable core_control and enable msm_thermal. As i found out after i play some really intensive gpu game, when phone slightly heat up(warm), my whole phone freezed, i suspect core_control trying to lower the voltage more and cause issue. Ever since i disabled core_control and switch to msm_thermal, no such issue happens anymore.

What an absolute legend. I'm running underclocked & well optimized kernel with HW overlays disabled (you can find the init.d script in xda) and the performance/battery life are both phenomenal, now this? My phone is just sipping the juice promille at time

Will it work with oos stock rom and stock Kernel?

Does this mod get removed after flashing a new ROM or update? I have installed and love it but I am not sure if it stays undervolted after flashing a ROM and don't want to apply it twice and break my phone if it does

For me -110mv is the limit for cpu. 120 becomes unstable, 130 doesnt boot. Running gpu on -190 for now
So -100mv cpu -190 gpu.

gsser said:
For me -110mv is the limit for cpu. 120 becomes unstable, 130 doesnt boot. Running gpu on -190 for now
So -100mv cpu -190 gpu.
Click to expand...
Click to collapse
Which kernel are you on?