Related
These registry entries control wmvdecoder.dll behaviour when playing WMV content on Windows Media Player 10. The keys are almost the same as they exist on the XP PC. You can use RegMon.exe to examine them on the PC. Some values are a little different.
The values starting with _ are not active.
"Post Process Mode" can range from 0 (no) to 4 (max) and when -1 it goes into auto mode.
[HKEY_CURRENT_USER\Software\Microsoft\Scrunch]
"Force Post Process Mode"=dword:00000001 ; obvious
"Adapt MHz"=dword:00000000 ; adapt the CPU clock frequency?
"_Current Post Process Mode"=dword:ffffffff ; this key should always be -1?
"Adapt QPC Level 0"=dword:00000014 ; ?
"Adapt QPC Level 1"=dword:00000028
"Adapt QPC Level 2"=dword:0000003c
"Post Process Mode"=dword:00000000 ; mode to use now
"Count CPU Cycles"=dword:00000000 ; ?
"_Adapt Post Process Mode"=dword:00000001 ; make it dynamic (works on PC)
"Omit BF Mode"=dword:00000000 ; ?
"Fake Player Behind"=dword:00000000 ; ?
[HKEY_CURRENT_USER\Software\Microsoft\Scrunch\Video]
"Bitrate"=dword:00000100 ; 256 kbs
"_Resolution"=dword:00014000 ; ?
So a lot of unknows in the equation here.
Also GAPI is used with WMP. I will place the keys tonite.
Still experimenting with the \windows\gxdma.dll (see attachement)
(\windows\gx.dll should be present in ROM)
WMP looks up these registry entries.
It can use GDI or GAPI.
[HKEY_CURRENT_USER\Software\Microsoft\MediaPlayer\Preferences]
"RenderGDI"=dword:00000000 ; use GDI instead of GAPI?
[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\MediaPlayer\GAPI]
"Buffer"=dword:00025800 '; 320x240x2
"DeviceID"=hex:\
01,00,02,00,E6,4C,B4,6D,32,33,32,39,30,37,14,14,09,04,01,02
"cbxPitch"=dword:00000002 ; pixel shift in buffer for 1 x pixel on screen
"cbyPitch"=dword:00000640 pixel shift in buffer for 1 y pixel on screen
"cBPP"=dword:00000010 ; 16 bitsperpixel
"cxWidth"=dword:000000f0 ; 240 pixel
"cxHeight"=dword:00000140 ; 320 pixel
"ffFormat"=dword:000000a8 ; have seen A0 as well
These values are a big dunno. Got them from a SNES emu site.
Also the DeviceID is hard to find. I just copied the
[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\MSLicensing\HardwareID]
"ClientHWID"=hex:\
01,00,02,00,E6,4C,B4,6D,32,33,32,39,30,37,14,14,09,04,01,02
Then you can put gxdma.dll in the \windows directory. Still investigating if that is improving performance.
I also try to use divx codecs with WMP10 CE. It can be done.
To be continued
Cheers
tweakradje said:
When running WMP 10 and CE Regspy I found these strange (very undocumented) registry entries that look kinda exiting:
Click to expand...
Click to collapse
And they look exciting because....?
tweakradje said:
These registry entries control wmvdecoder.dll behaviour when playing WMV content on Windows Media Player 10. The keys are almost the same as they exist on the XP PC. You can use RegMon.exe to examine them on the PC. Some values are a little different.
The values starting with _ are not active.
"Post Process Mode" can range from 0 (no) to 4 (max) and when -1 it goes into auto mode.
[HKEY_CURRENT_USER\Software\Microsoft\Scrunch]
"Force Post Process Mode"=dword:00000001 ; obvious
"Adapt MHz"=dword:00000000 ; adapt the CPU clock frequency?
"_Current Post Process Mode"=dword:ffffffff ; this key should always be -1?
"Adapt QPC Level 0"=dword:00000014 ; ?
"Adapt QPC Level 1"=dword:00000028
"Adapt QPC Level 2"=dword:0000003c
"Post Process Mode"=dword:00000000 ; mode to use now
"Count CPU Cycles"=dword:00000000 ; ?
"_Adapt Post Process Mode"=dword:00000001 ; make it dynamic (works on PC)
"Omit BF Mode"=dword:00000000 ; ?
"Fake Player Behind"=dword:00000000 ; ?
[HKEY_CURRENT_USER\Software\Microsoft\Scrunch\Video]
"Bitrate"=dword:00000100 ; 256 kbs
"_Resolution"=dword:00014000 ; ?
So a lot of unknows in the equation here.
Also GAPI is used with WMP. I will place the keys tonite.
Still experimenting with the \windows\gxdma.dll (see attachement)
(\windows\gx.dll should be present in ROM)
WMP looks up these registry entries.
It can use GDI or GAPI.
[HKEY_CURRENT_USER\Software\Microsoft\MediaPlayer\Preferences]
"RenderGDI"=dword:00000000 ; use GDI instead of GAPI?
[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\MediaPlayer\GAPI]
"Buffer"=dword:00025800 '; 320x240x2
"DeviceID"=hex:\
01,00,02,00,E6,4C,B4,6D,32,33,32,39,30,37,14,14,09,04,01,02
"cbxPitch"=dword:00000002 ; pixel shift in buffer for 1 x pixel on screen
"cbyPitch"=dword:00000640 pixel shift in buffer for 1 y pixel on screen
"cBPP"=dword:00000010 ; 16 bitsperpixel
"cxWidth"=dword:000000f0 ; 240 pixel
"cxHeight"=dword:00000140 ; 320 pixel
"ffFormat"=dword:000000a8 ; have seen A0 as well
These values are a big dunno. Got them from a SNES emu site.
Also the DeviceID is hard to find. I just copied the
[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\MSLicensing\HardwareID]
"ClientHWID"=hex:\
01,00,02,00,E6,4C,B4,6D,32,33,32,39,30,37,14,14,09,04,01,02
Then you can put gxdma.dll in the \windows directory. Still investigating if that is improving performance.
I also try to use divx codecs with WMP10 CE. It can be done.
To be continued
Cheers
Click to expand...
Click to collapse
Any news? It's interesting
buffer Size
So do you know if there is a Reg Key to increase the buffer size for streaming video?
Yhanks
Just wanted to confirm...
1. HKLM / Drivers / TouchPanel
Threshold to FFFFFFFF hex
2. HKLM / Software / OEM / TFLOSettings
FingerPressure to about 11000 dec
1. These are the only two things you can do to increase sensitivity / responsiveness of a ts correct?
2. If these are the 2 right and only keys...any opinions on what they should be set to? Do you guys think those are the best values?
Thanks.
Hello I'm trying to use xmlprovisioning to customize some features of S2U2.
An example of one key I'm having problem with is the following:
<parm name="ShowOwnerInfo" datatype="binary" value="01"/>
I just cannot get the value of 01 to stick. When I go back into S2U2 registry setting it is still showing as value not being set (according to CeRegistryEditor).
I don't have any problems changing other datatypes, such as: integer and string.
Am I don't something wrong?
Thank you in advance for all you guy's help.
Okay, I think I found out the reason:
"Binary values are a PITA since they're encoded Base 64 (see my entry for Owner Information above). If you want to set owner information as I did in the example, then you need to convert Unicode to Base64."
from: http://forum.xda-developers.com/showthread.php?t=366337&highlight=user+customization+binary
Can someone walk me through how to do this?
Is this any good?
Unicode to Base64 Convertor
Thank you for the suggestion.
I have already tried the tool, but what it gives me does not generate the effect that I'm looking for
Maybe I need to manipulate the value some how and then put it into the encoder??
Hi,
just an idea:
Binary data are hex ... so i attached a little txt ... just rename it and import to your registry.
It show how Binary-Values work (as far as i understood them )
In HKLM you'll find a Key (Folderlike) called "fwt"
Therein are three values
1. Capital
2. SmallLetter
3. Test
1. => FWT as binary data => 46,57,54
2. => fwt as binary data => 66,77,74
3. => all signs (letters, numbers, symbols) from 00 to FF
Space is 20
CapitalLetter start with 41
SmallLetters start with 61
Just use CeRegistryEditor and you can see them clearly .
I hope this helps!
Hi
Any ideas on how to adjust the a2dp bitpool settings. I am coming from windows mobile where this was easy to do in the registry. The stock bitpool seems to be 32 as per the logcat readout below. This is coming from an Evo 4G:
W/BTLD ( 1677): ### :: codec open ::
W/BTLD ( 1677): ### mtu 512, 660 bytes/frame, bitrate 229, nbr ch 0, freq 240
W/BTLD ( 1677): ### alloc : 3, blk len 240, chmode:15, bitpool 32:2, subbands 12
the sound is ok but could be better.
Another interesting part of the logcat is:
V/A2dpAudioInterface( 136): setParameters() bt_headset_name=DRC-BT15;bt_headset_nrec=on
E/AudioHardwareQSD( 136): setParameters() bt_headset_name=DRC-BT15;bt_headset_nrec=on
I/AudioHardwareQSD( 136): Using default acoustic parameters (DRC-BT15 not in acoustic database)
(I wonder what the acoustic database is.)
Any suggestions would be welcome. I did search around and found nothing easily implemented. Also nothing on the market.
Thanks
I want to know the exact same thing and not ready to accept that WinMo is superior to Android in any way...
I just found this page here which discuss some terminal and backend files in OSX for modifying these settings. Is there any similar file or terminal command we can do on our own unix based systems?
I have spent the last couple of weeks working on this and have come up with nothing. But I am not a programmer. Hope someone knows where to make the changes.
any update on this?
I am no programmer in any way, but I would realy like to know the outcome of this thread because it's been bugging me since I bought my Desire. I realy can't stand the loss of sound quality when listening to music on a bluetooth headset with my sennheiser headphones(HD215) connected.
I was wondering about the same thing. I used to tweak my WinMo Bitpool and samplerate. Any way to do this on Android?
I have been following this too. There must be a way to edit this somehow!! The a2dp quality of the evo/desire is awful! Must find a way!!!
I'm also disappointed in the audio quality on my Desire. I use my phone to listen to music in my car or mobile speaker via bt. But there are many tracks with high frequencies (or frequencies in some range), that causes some really disturbing clicking noise! Which I don't had on my Nokia N82 and SE K800i.
This really annoys me, and I consider to change to a different phone if there will not be a solution I'm currently using the original HTC firmware/radio, because I haven't rooted my phone yet. Is it possible that flashing a different radio will help?
I'm not sure if this is caused by the bitpool setting.
I will try to capture/upload some fragment with this clicking...
Edit: The microphone isn't good enough to record the clicking, but this fragment illustrates it very well (the clicking was actually in the track itself, but it sounds almost the same):
fragment (mp3)
Has there been any kind of an update on this one? A fix or a setting that could be changed?
I'm thinking of buying a Desire Z, but I will certainly stick to my ancient Touch Pro if the A2DP quality on Android is as bad as you all say. Bitpool of 32 is unlistenable, and I can't believe that neither Google nor HTC care about it.
Now that Cyanogen has fixed this in their ROM, I don't understand why no one has released a method for people not running Cyanogen.
So it has been fixed? What bitpool does that ROM run? I can't seem to find any info :S
And will they make a ROM for Vision with that fix?
I know I've got stupid noobish questions, but I'm completely new to the whole Android story and I haven't used these forums for ages so I'm quite lost atm...
CM6 is running 53
Thanks for the info
I'm having issues with an epic I just got (luckily in the 30 day return period). The a2dp audio sounds like garbage. The a2dp audio on my touch pro stock (before tweaked) was much better.
This could be a dealbreaker for me.
naorion said:
Now that Cyanogen has fixed this in their ROM, I don't understand why no one has released a method for people not running Cyanogen.
Click to expand...
Click to collapse
This is good news, but surely Mr.Cyanogen can pass on his method to Cotulla or one of the other primary Android Devs.... Hmm!
Any news on this? I flashed to Cyanogen 6.1. A2DP sounds much better. I now have mulitple exchange accounts working. The few issues are the Expensify receipt image capture does not work, 4G and HDMI also (know issues). I hope someone can find a fix for this.
I had a look at the bluez source code posted on HTC's developer site and I believe this is where the bitpool value is being set:
Code:
supersonic_bt.zip/external/bluetooth/bluez/liba2dp.c:
static uint8_t default_bitpool(uint8_t freq, uint8_t mode)
...
case BT_SBC_SAMPLING_FREQ_44100:
switch (mode) {
case BT_A2DP_CHANNEL_MODE_MONO:
case BT_A2DP_CHANNEL_MODE_DUAL_CHANNEL:
return 31;
case BT_A2DP_CHANNEL_MODE_STEREO:
case BT_A2DP_CHANNEL_MODE_JOINT_STEREO:
return 53;
default:
ERR("Invalid channel mode %u", mode);
return 53;
}
Changing the "return 31;" to "return 53;" and recompiling -or- hex editing the binary liba2dp.so on the phone ought to do the trick.
The same code block also appears in ipctest.c, pcm_bluetooth.c, sink.c, and source.c, so one or more of those files may also need to be modified.
I just got my Evo and I don't know enough about it yet to try this myself, but if someone else is able to then I think we'd all appreciate it if you could give it a shot. (Not all of us are interested in running a custom ROM just to fix this one problem.)
Edit: Another way may be to just force your desired min and max bitpool settings in the function bluetooth_a2dp_init():
Code:
cap->min_bitpool = min_bitpool;
cap->max_bitpool = max_bitpool;
Disregard that last post of mine. I had another look at liba2dp.c as well as some D/A2DP log output. All of the log output I could find posted online contains "channel_mode: JOINT STEREO", which according to default_bitpool() means the "default" bitpool should be 53. I originally thought the problem might be the bitpool setting of 31 referenced in that function, but I could not find any log output that contained "channel_mode: DUAL CHANNEL". (It shouldn't be too hard to verify this.)
So why is a lower bitpool value used? Look at this code snippet from bluetooth_a2dp_init():
Code:
min_bitpool = MAX(MIN_BITPOOL, cap->min_bitpool);
max_bitpool = MIN(default_bitpool(cap->frequency,
cap->channel_mode),
cap->max_bitpool);
cap->min_bitpool = min_bitpool;
cap->max_bitpool = max_bitpool;
The max_bitpool value is set to the lower of 1) the "default" bitpool and 2) the max bitpool reported by the audio sink (ie. your headset). If your headset reports a max bitpool of 32, then that is what will be used since it is less than 53. My understanding of the bluetooth spec is that audio sinks are supposed to accept bitpool values higher than 32 in order to support up to 512 Kb/s audio. Lower bitpool settings are more reliable, though, so perhaps that is why many headsets are configured to report artificially low values.
The actual bitpool value used is simply max_bitpool. See bluetooth_a2dp_setup():
Code:
data->sbc.bitpool = active_capabilities.max_bitpool;
The a2dp code isn't set up to take bitpool parameters from a configuration file, so liba2dp.c will need to be modified and recompiled. Possible quick fixes would be to change the "max_bitpool = MIN(" line to "max_bitpool = MAX(" or to manually set your desired bitpool value (ie. "data->sbc.bitpool = 53").
Hi,
I just want to say that since unfortunately my programming capabilities are close to non-existent I'm afraid I'm not able to provide much actual help in solving this issue but i highly appreciate that there are people who are looking into this and trying to remedy what Android OS designers and phone manufacturers neglected. I've been using A2DP headsets for the past 3-4 years with Nokia E51 and E52 phones which provided very good sound quality virtually indistinguishable from a cable connection and now after buying a Samsung Galaxy S phone I'm terribly disappointed at its A2DP performance comparable to 112kbps MP3s with even the highest quality sources.
I own three different A2DP headsets manufactured by Sony Ericsson, Nokia and unnamed Chinese labourers respectively and a set of quality IEM earphones plugged into quite good and relatively trained ears. Since A2DP support on both Nokias and a Samsung Blackjack I owned shortly (and let go of just because of its pitiful A2DP performance) has not always been perfect I know a thing or two about how A2DP works and performs. So if there is anything I can do to help regarding testing, preparing and submitting logs etc. just let me know and I will be very happy to help if that's what is needed.
Thanks!
Petr
I have a HTC Trophy, coming from a HTC Touch Pro 2. The speaker phone was awsome on the TP2 and on the trophy, if there is small noises in the room (even a low computer fan) with the phone on mute, you can bearly hear the people on the phone. It's so low that with any low background noise, it's hard to hear.
Is it possable to increase the volume on the speaker phone on WP7 higher than 10 (maybe up to 15 or so) ???
Thanks !
TP2 has the best spekaer phone ever! It is highly unlikely that Trophy (or any other, I have HTC 7 Pro and spekaer phone is not as good as TP2) can reach it, maby by changing rege, but it can only harm the speaker since it will be overloaded.
I, too, miss TP2 speaker phone and talking in the car without jelling...
DavidinCT said:
I have a HTC Trophy, coming from a HTC Touch Pro 2. The speaker phone was awsome on the TP2 and on the trophy, if there is small noises in the room (even a low computer fan) with the phone on mute, you can bearly hear the people on the phone. It's so low that with any low background noise, it's hard to hear.
Is it possable to increase the volume on the speaker phone on WP7 higher than 10 (maybe up to 15 or so) ???
Thanks !
Click to expand...
Click to collapse
There is a registry edit to increase the # of increments, but it doesn't increase volue at all. It just adds more "steps". Haven't found anyway to increase the volume. It seems to be a driver issue on all HTC devices. HTC needs to get their act together & issue a patch to fix this. It's almost impossible to hear music/videos/movies. Any background noise & you can't hear ****.
I think I just fixed this. I saw a registry edit for WM 6 & it the directory still exists.
HKCU\ControlPanel\SoundCategories\
In each of it's sub directories, change the InitVol value to 100. I notice some were 100 already while others were 85 or even 65. I think this means 100% volume/85% volume/65% volume. Change them all to one value & you'll equalize the volume across the board.
drkfngthdragnlrd said:
I think I just fixed this. I saw a registry edit for WM 6 & it the directory still exists.
HKCU\ControlPanel\SoundCategories\
In each of it's sub directories, change the InitVol value to 100. I notice some were 100 already while others were 85 or even 65. I think this means 100% volume/85% volume/65% volume. Change them all to one value & you'll equalize the volume across the board.
Click to expand...
Click to collapse
Doesn't this just, like you said, increse the step but, not give a higher volume ?
SHould I be opening a ticket with HTC about this ?
DavidinCT said:
Doesn't this just, like you said, increse the step but, not give a higher volume ?
SHould I be opening a ticket with HTC about this ?
Click to expand...
Click to collapse
No, this is different. I just found it. The registry value I was talking about before is;
HKCU\ControlPanel\Volume\
MaxInCallUIVolume & MaxSystemUIVolume
I just did this new edit I just found (this one in the above post) & now I can hear youtube videos over my pc with tv playing on it lol.
thanks, I just gota figure out how to edit the registry with mango and I'll give it a shot.
drkfngthdragnlrd said:
No, this is different. I just found it. The registry value I was talking about before is;
HKCU\ControlPanel\Volume\
MaxInCallUIVolume & MaxSystemUIVolume
I just did this new edit I just found (this one in the above post) & now I can hear youtube videos over my pc with tv playing on it lol.
Click to expand...
Click to collapse
LG quantum here:
this is what it reads (dword)
HKCU\ControlPanel\Volume\
MaxInCallUIVolume = 10
MaxSystemUIVolume = 30
you set yours to 100?
also, I am not sure from your two posts, which one was necessary to get your volume up to max - entries from both posts?
with MFG I am not able to see the subcategories you mention in the post before under "SoundCategories". So I would have to query "blind" keys. too many to type them here?
thanks
derausgewanderte said:
LG quantum here:
this is what it reads (dword)
HKCU\ControlPanel\Volume\
MaxInCallUIVolume = 10
MaxSystemUIVolume = 30
you set yours to 100?
also, I am not sure from your two posts, which one was necessary to get your volume up to max - entries from both posts?
with MFG I am not able to see the subcategories you mention in the post before under "SoundCategories". too many to type them here?
thanks
Click to expand...
Click to collapse
No, that is the "steps". It just adjust how many increments you have. It's the other post.
HKCU\ControlPanel\SoundCategories\
In each of it's sub directories,
InitVol = 100
You can adjust the volume done for those who complain about the volume being too loud by entering a lower value.
drkfngthdragnlrd said:
No, that is the "steps". It just adjust how many increments you have. It's the other post.
HKCU\ControlPanel\SoundCategories\
In each of it's sub directories,
InitVol = 100
You can adjust the volume done for those who complain about the volume being too loud by entering a lower value.
Click to expand...
Click to collapse
thanks, problem with the MFG registry editor is that it does not show the sub directories. One would have to enter them before they can be edited, therefore one would need to already know the names of the sub categories.
thanks again
derausgewanderte said:
thanks, problem with the MFG registry editor is that it does not show the sub directories. One would have to enter them before they can be edited, therefore one would need to already know the names of the sub categories.
thanks again
Click to expand...
Click to collapse
Alarm\
DTMF\
InCall\
InCall2\
Notification\
Reminder\
Ring\
RingPreview\
System\
SystemNotification\
SystemVibrate\
drkfngthdragnlrd said:
Alarm\
DTMF\
InCall\
InCall2\
Notification\
Reminder\
Ring\
RingPreview\
System\
SystemNotification\
SystemVibrate\
Click to expand...
Click to collapse
terrific and thank you
what is DTMF? default on the LG is 65
(System = 85, SystemNotification = 85, SystemVibrate = 85, the rest is on 100)
derausgewanderte said:
what is DTMF? default on the LG is 65
(System = 85, SystemNotification = 85, SystemVibrate = 85, the rest is on 100)
Click to expand...
Click to collapse
I have no clue what DTMF is. I believe the value stands for % of max volume. I set them all to 100. Now I may just be hearing things, but it sure sounds louder to me. I had the TV playing on my PC & the YouTube video on my HD7 droned out the TV. (heard YouTube Video clearly, but couldn't here TV). Now keep in mine I have 200 Watt RMS Logitech 2.1 Speakers w/a Sub Woofer on my PC & they were at 33% volume.
as most are on mango now...
so the subcategories are named...can you name the keys to edit?
even better would be a *.reg-file we can provxml
diboze said:
as most are on mango now...
so the subcategories are named...can you name the keys to edit?
even better would be a *.reg-file we can provxml
Click to expand...
Click to collapse
see drkfngthdragnlrd's post #9, they key is the same for all:
InitVol = 100
change the number you find to 100. Most of them are already on 100.
drkfngthdragnlrd said:
I have no clue what DTMF is. I believe the value stands for % of max volume. I set them all to 100. Now I may just be hearing things, but it sure sounds louder to me. I had the TV playing on my PC & the YouTube video on my HD7 droned out the TV. (heard YouTube Video clearly, but couldn't here TV). Now keep in mine I have 200 Watt RMS Logitech 2.1 Speakers w/a Sub Woofer on my PC & they were at 33% volume.
Click to expand...
Click to collapse
DTMF (dual tone multi frequency) is the signal to the phone company that you generate when you press an ordinary telephone's touch keys. In the United States and perhaps elsewhere, it's known as "Touchtone" phone (formerly a registered trademark of AT&T). DTMF has generally replaced loop disconnect ("pulse") dialling. With DTMF, each key you press on your phone generates two tones of specific frequencies. So that a voice can't imitate the tones, one tone is generated from a high-frequency group of tones and the other from a low frequency group.
:http://searchnetworking.techtarget.com/definition/DTMF
derausgewanderte said:
see drkfngthdragnlrd's post #9, they key is the same for all:
InitVol = 100
change the number you find to 100. Most of them are already on 100.
Click to expand...
Click to collapse
Hi,
You did not understand. After update to Mango there is no possibility to edit registry yet. So we need a full code to do it by provxmal. If you have access you can do it for us.
PanNet said:
Hi,
You did not understand. After update to Mango there is no possibility to edit registry yet. So we need a full code to do it by provxmal. If you have access you can do it for us.
Click to expand...
Click to collapse
I do understand. if you want to inject this into the registry via provxmal then you need to convert this into code for the registry, no?
[HKEY_CURRENT_USER\Control Panel\SoundCategories\Alarm\]
"InitVol"=dword:00000064
or
"InitVol"=hex(b):64,00,00,00,00,00,00,00
(100 dec = 64 hex). I am sure the programmers here know exactly what to do with it.
and the same for
DTMF\; InCall\; InCall2\; Notification\; Reminder\; Ring\; RingPreview\; System\; SystemNotification\; SystemVibrate\
but maybe I am missing something....
PanNet said:
Hi,
You did not understand. After update to Mango there is no possibility to edit registry yet. So we need a full code to do it by provxmal. If you have access you can do it for us.
Click to expand...
Click to collapse
EDIT: Speaking of which, I found another registry that deals with how audio is handled. Attached is the provxml for it. This CustClear.provxml has all the volume registry edits I have done. It give you 50 steps for volume in call & default system.
derausgewanderte said:
I do understand. if you want to inject this into the registry via provxmal then you need to convert this into code for the registry, no?
[HKEY_CURRENT_USER\Control Panel\SoundCategories\Alarm\]
"InitVol"=dword:00000064
or
"InitVol"=hex(b):64,00,00,00,00,00,00,00
(100 dec = 64 hex). I am sure the programmers here know exactly what to do with it.
and the same for
DTMF\; InCall\; InCall2\; Notification\; Reminder\; Ring\; RingPreview\; System\; SystemNotification\; SystemVibrate\
but maybe I am missing something....
Click to expand...
Click to collapse
Hi,
Thanks. Can you write default settings for InCall, InCall2, Ring, RingPreview.