Has anyone discovered one yet ?
I've tried this:
HKLM\Software\Microsoft\Bluetooth\AudioGateway\Spk Volume
(DWORD:10)(Default:5)
But I don't have that key in the registry.
t-mobile Vario III - standard 1.56.110.4 ROM
compact_bijou said:
Has anyone discovered one yet ?
I've tried this:
HKLM\Software\Microsoft\Bluetooth\AudioGateway\Spk Volume
(DWORD:10)(Default:5)
But I don't have that key in the registry.
t-mobile Vario III - standard 1.56.110.4 ROM
Click to expand...
Click to collapse
Where is that value from?
Web search pulled up this: http://forum.ppcgeeks.com/showthread.php?t=7715
So I navigated to the relevant section of the registry to see if there were any corresponding values. I know the phone is a different model,
I'm just trying to get some idea of where the bluetooth audio settings might be in the registry.
compact_bijou said:
Web search pulled up this: http://forum.ppcgeeks.com/showthread.php?t=7715
So I navigated to the relevant section of the registry to see if there were any corresponding values. I know the phone is a different model,
I'm just trying to get some idea of where the bluetooth audio settings might be in the registry.
Click to expand...
Click to collapse
ok, try to add the values.
Does it make any change?
Nadavi
how do we get the day of the week to show on the htc home screen?
I use to ba able to do it with pimp my black on the 8525 by adding "dddd" in front.
anyone know the registry for this function
Agreed - This would be handy!!
I haven't found anything in the registry for this, the date displayed in the HTC Home Plugin appears to be hardcoded to use the "short date" formating.
greg3d said:
I haven't found anything in the registry for this, the date displayed in the HTC Home Plugin appears to be hardcoded to use the "short date" formating.
Click to expand...
Click to collapse
HKLM/nls/overrides/SSDte
add ",ddd" at the end of the string.
Universal owner with Homeplug...
Hi,
I don't have a Kaiser but I'm running the homeplug on a Universal and I'd just like to know what the string is before the ",ddd" in your registry . For some reason it doesn't recognise dd/mm/yy it just displays the day 05/mm/07, Mon.
Thanks.
Edit : Don't worry figured it out it has to be dd/MM/yy or dd/MM/yyyy then space or , "ddd" (3 letter day) or can be "dddd" (Full day name)
For short day and month as shown here:
HKLM/nls/overrides/
Change SLDte and SSDte to: ddd, MMM dd, yyyy
Maybe it's too early but I have no keys in \HKLM\nls\overrides\
would manually creating the keys work? what are the values/names etc. if so?
Thanks - this is exactly what I've been looking for if it works!
EDIT: Using AT&T Tilt
jeffreii said:
Maybe it's too early but I have no keys in \HKLM\nls\overrides\
would manually creating the keys work? what are the values/names etc. if so?
Thanks - this is exactly what I've been looking for if it works!
EDIT: Using AT&T Tilt
Click to expand...
Click to collapse
I don't have that keys either... can you tell me what exactly you did?
jeffreii said:
Maybe it's too early but I have no keys in \HKLM\nls\overrides\
would manually creating the keys work? what are the values/names etc. if so?
Thanks - this is exactly what I've been looking for if it works!
EDIT: Using AT&T Tilt
Click to expand...
Click to collapse
Go into your Regional settings and change the date format, it will create those registry keys for you to edit afterwards.
jeffreii said:
Maybe it's too early but I have no keys in \HKLM\nls\overrides\
would manually creating the keys work? what are the values/names etc. if so?
Thanks - this is exactly what I've been looking for if it works!
EDIT: Using AT&T Tilt
Click to expand...
Click to collapse
Manually creating the keys works:
\HKLM\nls\overrides\SLDte (Format: string) Value: dddd, MMMM d, yyyy
and
\HKLM\nls\overrides\SSDte (Format: string) Value: dddd, MMMM d, yyyy
(or choose the type of date you want)
i removed the ", yyyy" as i think the year is not necessary and it was messing up my call history.
the part that shows the date of the call was too long and was cutting off the name/number of the caller. removing the year shortens it a bit and minimizes the problem.
thanks again for this tweak!
jeffreii said:
i removed the ", yyyy" as i think the year is not necessary and it was messing up my call history.
the part that shows the date of the call was too long and was cutting off the name/number of the caller. removing the year shortens it a bit and minimizes the problem.
thanks again for this tweak!
Click to expand...
Click to collapse
I found using SSDt2 as "ddd, M/d/yy" is a good compromise and only interferes with call hsitory when the caller's name is very long.
greg3d said:
I found using SSDt2 as "ddd, M/d/yy" is a good compromise and only interferes with call hsitory when the caller's name is very long.
Click to expand...
Click to collapse
I try manually enter the key...didnt work.
I made a new key (sub-directory) called "SSDt2"...Name: "Format: string"...Data: "ddd, M/d/yy
I am using PHM
Works great on TC
Thanks this works perfect on my Touch Cruise, there was so much information on the HTC home screen, except day!! This solved it.
borealcool said:
Go into your Regional settings and change the date format, it will create those registry keys for you to edit afterwards.
Click to expand...
Click to collapse
That was an awesome answer to a plea for help! Thank you for replying with no scolding or sarcasm! Thank you!!!
When I uninstalled the keypad vibrate app, my keypads no longer worked properly. I reviewed this registry key on my device and it's messed up pretty bad (sound settings for each button are not correct).
Can someone export the complete HKCU\ControlPanel\Sounds to a .reg file, zip, and post here please?
Here's the entire set of keys you wanted.
outphase said:
Here's the entire set of keys you wanted.
Click to expand...
Click to collapse
thanks, that helps...
can you do me one more export? I also need HKLM/snd
Have been sniffing around my registry for another reason and stumbled on the reg key ... HKLM\init\BootVars\RequireCertmod ....
It has a value of 1
I really am just guessing but would setting it to 0 allow uncertified ROMS to be installed ?
I don't know what this key do, but it certainly has nothing to do with ROM flashing.
macdat said:
Have been sniffing around my registry for another reason and stumbled on the reg key ... HKLM\init\BootVars\RequireCertmod ....
It has a value of 1
I really am just guessing but would setting it to 0 allow uncertified ROMS to be installed ?
Click to expand...
Click to collapse
nope nothing to do with registry
talking about registry tweaks
can someone point me in the direction of the tweak for gps info within a picture and IMPORTANTLY method & software required to make the tweak... cheers mark
I recently flashed a new ROM to my diamond and the camera image counter (the automatic naming of the images) reset to 1
Is there a registry key where that number is stored, so i can change it back to the old value(600) ?
Thanx
HKLM\Software\HTC\Camera\Captparam\ExifInfo
NEXTFILENAME key
change the number to what you want the next imagename to use.
It didn't work
I changed NEXTFILENAME key from IMAGE_005 to IMAGE_700, but the next image I take is IMAGE_005, and the key changed back
I even tried to change the key then soft-reset but same thing happened.
Doesn't anyone have another ideea? This should be easy.
I really need this because I take alot of photos and I can't organise them anymore.
isnt it in the settings for the camera? pretty sure i have seen it there....
mugglesquop said:
isnt it in the settings for the camera? pretty sure i have seen it there....
Click to expand...
Click to collapse
I can only reset it there.
supersanj said:
HKLM\Software\HTC\Camera\Captparam\ExifInfo
NEXTFILENAME key
change the number to what you want the next imagename to use.
Click to expand...
Click to collapse
Hi, is there anybody who knows how to manage this issue with a TouchPro2?
regarda
Rob
Found the answer in another post:
http://forum.xda-developers.com/showthread.php?t=439035
anne9660 said:
Found the answer in another post:
http://forum.xda-developers.com/showthread.php?t=439035
Click to expand...
Click to collapse
I found this posting before but because byte 68 and 69 are zero I thought this post did not cover my device.
Now I looked a little deeper and found byte 109 and 110 which are the right ones for my Touch Pro2. And it works!