Database Info

reg key!

is possible for you to put in only one topic All the best reg key adjustement?
i'm a newbie but i would learn quikly..
many thx!

Try to use usenet instead of this forum. It's a little bit illegal

I think Bubu try to search Registry key and not Registration key :wink:

You are right. I'm sorry
In that case:
Dunno if you've all seen this before but you can speed up your JAM by doing the following:
1) Go to HKEY_LOCAL_MACHINE\SYSTEM\GDI\GLYPHCACHE
2) Change the value of 'limit' from 8192 to 32768
3) Soft reset.
this was posted at: http://www.ppcsg.com/index.php?showtopic=45733
I did it to my JAM...no problems so far. Does seem to be a tad faster in loading apps...remember to backup before messing with Registry values!
Click to expand...
Click to collapse
Manual at every sms:
Tooltje download: TRE Registry Editor
To start up --> HKEY_CURRENT_USER/Software/Microsoft/Inbox/Setting
(care that those are open)
New - > DWORD
name: SMSDeliveryNotify
value: 1
(Should you nothing see because your keyboard in the way sits, simply blind "SMSDeliveryNotify" type (without quotations mark with
head and small characters) followed by grapple, the value comes afterwards, however, click him 1x (select) and click then on edit - > modify - > "1"
indicate value)
sounds more with difficulty than it is...
Click to expand...
Click to collapse
The last quote is from a translate site. (Dutch --> English). Maybe you can use them eiher. It's works prette good @ me

Take a look at this thread:
http://forum.xda-developers.com/viewtopic.php?t=20119

Strange WMPlayer related keys. Who knows them?

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

Audiogain Questions

I have some questions about the audiogain registry settings.
Currently I'm using a Tornado smartphone with WM6 (standard).
I would specifically like to increase the volume output to my AD2P bluetooth headphones. Which keys are relevant?
But I do have more questions:
Are all keys supposed to be hex?
What are the limits for the hex data? (i.e. should it convert to a decimal value between 1-100, because I see some convert to decimal values of 179)
What is the deal with keys that have values like "60 63 66 23 26 29"?
TIA

Touchscreen Driver improvements (Touch.dll)

Touchscreen Driver improvements (Touch.dll)
This Polaris thread contains a new Touchscreen Driver and various registry keys to improve touchscreen response.
http://forum.xda-developers.com/showthread.php?t=446126
***WARNING***
Unfortunately, at this stage this improved touchscreen driver is not compatible with Kaiser Roms. Hopefully further testing and development with change this.
__________________
According to my Kaiser Taskmanager (I have tried this on at least 5 Roms and is a well know HTC bug on many devices), just placing pressure and motion on the touchscreen uses an addition 50%+ CPU usage even if no function is being accessed by touching the screen. Touchscreen driver is also at Highest Priority setting by default. This is a major cause of sluggishness on HTC devices as all tasks, including screen re-draws is suspended in favour of the touchscreen mindlessly using 50%+ CPU.
Creating this following registry keys can lower the CPU priority but the screen is very unresponsive -
HKEY_LOCAL_MACHINE\Drivers\BuiltIn\Touch
(DWORD)
Name = "Priority256"
Value = "255"
Name = "PriorityHigh256"
Value = "255"
The following registry keys (Original Microsoft value that can be found at MSDN for a normal driver) lower the CPU priority but still maintain usability (CPU can still reach 50%+) -
HKEY_LOCAL_MACHINE\Drivers\BuiltIn\Touch
(DWORD)
Name = "Priority256"
Value = "109"
Name = "PriorityHigh256"
Value = "109"
A soft reset is required to test these values. I am currently testing different values to find the best blend between screen response and screen refresh rate.
There are other registry keys which may help as well. I look forward to your feedback.
I am not a programmer but I started this thread in the hope that one of our highly talented chefs would be able to make a port of Polaris driver for Kaiser. I have tried playing with the registry and it does have an effect but there are trade-offs between graphics performance vs touch screen response.

TITAN-23 said:
Touchscreen Driver improvements (Touch.dll)
This Polaris thread contains a new Touchscreen Driver and various registry keys to improve touchscreen response.
http://forum.xda-developers.com/showthread.php?t=446126
According to my Kaiser Taskmanager (I have tried this on at least 5 Roms and is a well know HTC bug on many devices), just placing pressure and motion on the touchscreen uses an addition 50%+ CPU usage even if no function is being accessed by touching the screen. Touchscreen driver is also at Highest Priority setting by default. This is a major cause of sluggishness on HTC devices as all tasks, including screen re-draws is suspended in favour of the touchscreen mindlessly using 50%+ CPU.
Creating this following registry keys can lower the CPU priority but the screen is very unresponsive -
HKEY_LOCAL_MACHINE\Drivers\BuiltIn\Touch
(DWORD)
Name = "Priority256"
Value = "255"
Name = "PriorityHigh256"
Value = "255"
The following registry keys (Original Microsoft value that can be found at MSDN for a normal driver) lower the CPU priority but still maintain usability (CPU can still reach 50%+) -
HKEY_LOCAL_MACHINE\Drivers\BuiltIn\Touch
(DWORD)
Name = "Priority256"
Value = "109"
Name = "PriorityHigh256"
Value = "109"
A soft reset is required to test these values. I am currently testing different values to find the best blend between screen response and screen refresh rate.
There are other registry keys which may help as well. I look forward to your feedback.
Click to expand...
Click to collapse
Im thinking about doing the opposite. I want faster touch response. lol

TheParadox said:
Im thinking about doing the opposite. I want faster touch response. lol
Click to expand...
Click to collapse
Actually, the touch "user experienced" responsiveness is slower if the touch.dll has too high a priority as the screen refreshes slow down (lower frames per second on scrolling and animations).
Have you noticed that frames per second DECREASE dramatically the longer you touch the screen? This is because screen re-draws (refreshes) are at a lower priority to the touch driver. The touch driver is hogging the CPU. This makes the interface sluggish and slow.

resulted in a completely unresponsive touchscreen in my Kaiser .. hard reset was needed. Perhaps incompatible with the rom i was using? (Ultimate X v7 .. excellent rom btw).

bump
would love to see some progress made on this

When i saw the title i thought there was a new driver that was less cpu intensive . Oh well, i should give this a try and see if it is compatible with josh's kitchen.
Edit: there is a driver, but work on it appears to be discontinued?
This guy was doing the winmo world quite a favor by attempting to fix a problem that plagues us all (or at least the HTCers among us.) I wonder if htc will fix this eventually.

I am not a programmer but I started this thread in the hope that one of our highly talented chefs would be able to make a port of Polaris driver for Kaiser. I have tried playing with the registry and it does have an effect but there are trade-offs between graphics performance vs touch screen response.

marbella property
First Time it is worked for me, but now it is look like i have jailbreaked my device

bump.
as for me 2d drivers more important that 3d one.

It works
I'm currently using a value of 109 as recommended and feel it more responsive.
The ROM i'm using is Josh 21806 Full.

Help with UC and xml.

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!