Hello,
Does anyone have a cab version of the HTC camera delay fix cab. It is suppose to greatly reduce the time that the shutter releases from when the button is pressed. Searched this site and the internet with no luck.
I did find a post where a version that can be cooked into roms exists, but no cab.
http://forum.xda-developers.com/showpost.php?p=1676838&postcount=24
Note: The cab I am looking for is not the one that reduces the delay when storing videos on a memory card on the ELF.
Thanks in advance.
did you find a solution for this ?
As far as i can see all the above HTC camera delay fix in the link does is change the Delay value in [HKEY_LOCAL_MACHINE\Software\HTC\Camera\Captparam]
I think the default is 10 (0000000a) the reg fix changes this to 1.
You could try this out yourself with any of the free registry editors and see if it helps with your problem.
G
Related
:?: :idea:
I'm just finishing the next version of MY|PHONE|PROFILES.
http://www.geocities.com/myppcpe2003/
(on the bottom of the page there are screenshots of the upcoming version)
Beside the main purpose of this program - to change the Phone Profile in the one touch of the screen - I built there a few requested tweaks of PPC Phone Edition.
Like: clearing the database leak hotfix, change the low battery warning, lock all hardware keys except the power, wake-up the screen when new SMS message arrived, longer time of vibrating, and more. See the screenshots I will update daily.
Before I close the project, I'm awaiting your next suggestions, what others fixes to build in (only specified for PPC Phone Edition devices).
:arrow:
Ps. Please do not write "ring on speaker when headphone is connected". This is a hardware electrical switcher when you plug-in the headphone to cut-off the speaker part. No way to overwrite the speaker to play in this moment, as I understand.
JGUI said:
:?: :idea:
I just finishes the next version of MY|PHONE|PROFILES.
[...]
Before I close the project, I'm awaiting your next suggestions, what others fixes to build in (only specified for PPC Phone Edition devices).
Click to expand...
Click to collapse
Please make these tweaks registry-controlable, so I can set which ones to use from the ROMkitchen... Could you then also create reg-settings which would cause your program to set for 'use large keys/gestures' (my pref..), and menu animation ? (WM2003 resets these reg values at cold-boot...
Ps. Please do not write "ring on speaker when headphone is connected". This is a hardware electrical switcher when you plug-in the headphone to cut-off the speaker part. No way to overwrite the speaker to play in this moment, as I understand.
Click to expand...
Click to collapse
No, not true. I believe this is software setteable. (I need to figure this one out for my day-job also, so would appreciate pointers...)
What about beta versions?
Hi,
I got an O2 Comet (Atom Live). Also got a protective film on the touch screen.
Now the pressure needed to use the touch screen is quite high in my opinion.
Is it possible to tweak/change the threshold value for the touch screen via registry tweaks etc. ? Or is the touch screen sensitivity for the Atom Life not changeable?
I got Medkid's Atom Life WM6.1 ROM installed btw.
Thx for any help,
boba
Have you tried this??
HKEY_LOCAL_MACHINE\SOFTWARE\Drivers\Touch
or find 'Threshold'
Change the value of Pressure Threshold.(INCREASE value ONLY!!!)
Example, just set the value at 11880.
That doesn't exist in the registry
Any other suggestions?
Try and see if its in there,
HKEY_LOCAL_MACHINE\Drivers\TouchPanel
What registry editor are you using?
Search your registry for DWORD, "PressureThreshold".
Nope its not there I'm using resco registry editor
Ok download the registry editor below and install it. (phone or storage card it doesn't matter)
Run the app and it should start something like this...
SCREENSHOT_1
Make sure you highlight HKEY_Local_Machine like in the photo otherwise it won't search correctly
SCREENSHOT_2
Now click on "FIND"
SCREENSHOT_3
Copy what you see in the photo onto your phone and click "FIND NEXT"
SCREENSHOT_4
And it should come up with something, if not I don't know what to tell you the instructions I have given are as handicapped as possible.
SCREENSHOT_5
Hi, thanks for the help. It couldn't find the key either. I don't think atom life phones have this key. Are you using an atom life under WM6 too?
no, but there are plenty of posts where people have done it.
That posts I have read reference different registry locations, so I assume that the pressure configuration is set by each manufacturer.
The camera is slow on my 8525 (WM6). I press the button and 2-3 seconds later, the picture is taken. I saw a fix on here but it wasn't a CAB file so I didn't know how to use it...
Can anyone recommend a proceedure to fix this annoying issue?
I don't know of a cab that does the fix, the registry key is mentioned on the Camera Shutter Delay Fix Cab Request thread below in this forum and is easy to do.
G
Thanks for the info and the link. I've made the registry change therein and will see if it performs any more quickly.
Thanks again.
Try this... On my hermes, it will help and camera capture is very fast, after this registry modification...
HKEY_LOCAL_MACHINE/SOFTWARE/HTC/Camera/Captparam/
DeleyTime (set to1)
Thanks for your message. I've modified my registry.
I found the following problem with most cooked ROMs (also including the last official one from HTC) /I tried that on fresh installations in every case/
I like AutoLock feature. So I made a small .reg file to modify one small entry in registry.
The moment this feature is on - if the device becomes locked, the screen goes dim. Problem is - it stays dimmed forever. I tried thousand different solutions - many combinations of registry values, power options, etc. nothing helps. If I lock the device manually - no problem. only with autolock. Anybody knows how to make it work?
Regards,
Vojtek
Maybe you should post your script, so that someone can have a look. Did this work on some previous ROM? Or has it been an ongoing problem?
Try using SmartLock, found on this site.
jmckeejr said:
Maybe you should post your script, so that someone can have a look. Did this work on some previous ROM? Or has it been an ongoing problem?
Click to expand...
Click to collapse
The official HTC ROM that I used to have before recent official update from HTC - worked very fine with this little registry mod.
The modification is as follows:
HKCU->ControlPanel->Backlight->AutoDeviceLockEnable
default value = 0
I change it to 1. This is all I do after totally fresh ROM update. that causes the dim to go permanently on from the next lock (doesn't matter if it was caused by auto or manual). even If I get back with the value to 0 in registry - problem stays. soft reset (and value set to 0) eliminate the problem.
one more thing - I never use auto-light sensor. My backlight level is always set to 2. with auto-light sensor - autolock works OK. however I loose a lot of battery life since auto-light sensor never allows backlight levels lower than 4.
Regards,
Vojtek
check out Lumos, it'll let you backlight go as low as you set it to
http://forum.xda-developers.com/showthread.php?t=450318
GldRush98 said:
check out Lumos, it'll let you backlight go as low as you set it to
http://forum.xda-developers.com/showthread.php?t=450318
Click to expand...
Click to collapse
Thank You for the tip. The tool itself is great. However it is affected same way by the autolock. Autolock causes device to stay dimmed permanently - even with Lumos running.
Regards,
Vojtek
First off... I'm new around here & still a little flabbergasted by everything WinMo, but this site has already helped me tremendously.
Secondly, I can confirm the AutoLock bug. I updated my Touch Pro to the latest official rom last night. While running through AdvancedConfig (i think...) I noticed the AutoLock option & enabled it. 10 minutes later I was freaking out that I had stuffed up my expensive new toy...
Disabled, rebooted & all is OK again.
First of all - Advanced Config has nothing to do with it (to defend the author).
Second - thank You for support. I could not find a solution for this problem anywhere and I spent hours googling. For the moment I thought that my TP is failed. Seems that nobody uses AutoLock these days. I don't know how everybody's doing it, but without locking, my TP calls to different people (especially from Favourites tab) from time to time...
Vojtek
vojtek11 said:
I don't know how everybody's doing it, but without locking, my TP calls to different people (especially from Favourites tab) from time to time.
Click to expand...
Click to collapse
I require a password/passcode level of security on my device - which the Lock/Unlock feature doesn't provide. Unfortunately, the current security implementation in WinMO 6.x doesn't allow the Today screen to be seen like the Lock/Unlock feature.
As a result of these shortcomings, most folks tend to use a 3rd Party lock application such as: S2U2, mLock, etc. as they provide the desired flexibility.
HTH,
very familiar with this issue. I'm working on it too. It affects the WM6.5 lockscreen for sure and I thought it was a problem with only that. Bugger that it affects official ROMs as well. Good info though, I can stop concentrating on the lockscreen and start looking at power mgmt.
mindfrost82 said:
Try using SmartLock, found on this site.
Click to expand...
Click to collapse
SmartLock all the Way!!
Windows Mobile Version: 6.5
Manila Version: 2.5.20181527.0
ROM Version: 3.14.405.2 (04666) WWE
Hi, bought my HD 2 a week ago and every time I am in an active call the touch screen buttons don't seem to function. Specifically, the 'end call' touch screen button, menu buttons etc. The hardware buttons work fine, which is why I end the call using the end call hardware button.
Outside of an active call, the touch screen buttons work fine. Just seems to be during an active call.
Was wondering if there's any help on this. Seems to be like there's not a fault, but more like a restriction or something stopping the touch screen buttons from being able to function when in an active call. However, I'm a new HD 2 user so I am slightly inexperienced as to what to do.
Further info can be given if needed. Thanks and any help is appreciated
I have exactly the same problem after I installed ROM 3,14. After some tests, I found out, that the screen buttons are working if you hold and swipe carefully, but they are very unresponsive. I think there should be a registry tweak available for this - I tried to find hints in the XDA forums without any luck. Anyone could help?
I have the same problem with all of the 3.14 based roms too.Is there any help to solve this massive problem?
alijani said:
I have the same problem with all of the 3.14 based roms too.Is there any help to solve this massive problem?
Click to expand...
Click to collapse
I think I just found the solution - at least it worked for me...
Have you done the registry tweak #44 from the registry tweak thread? If yes, revert back, and voila, problem solved. I copy here for reference:
"44. Prevent Accidental Link Activation When Scrolling
Do you scroll and find you accidentally click on something? This tweak is for you. Note: Can cause problems for some so remember original value in case to revert back. Note: for some, users cannot tap on screen buttons during a call. Revert to original reg entry if this is the case.
HKLM/System/GWE/Touch/Filter/Minimumtaptime
Change from 0 to 30"