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"
Related
My new HTC S740 is excellent except for one thing - the keypad backlight goes out after only 15 seconds. Very irritating in the dark.
I've looked for kb_light_timeout in hklm/software/htc/keypad but this does not exist.
I've found keylight timeout and qkeyledtimeout in hkcu/control panel/backlight which looks like the right place but altering values and rebooting makes no difference.
I've also looked in hklm/drivers/builtin/keylight and keypad.
I feel I'm very close. Can anyone help?
Yes Its most annoying as well as fact that only numbers or keys round circular button light seperately. Look forward to someone cracking it. Otherwise an excellent phone.
I agree, this is very annoying.
So theres no fix for this issue? To bad no ACT for this phone. An awesome phone, just wm standard gets so little love it seems.
I did some research today and he're the results:
1. This is far of to be a new issue. First complaints about the keyboard backlight timeout you can find under Qtek models...
2. Apparently, they were just few (2-3?) HTC models supporting a registry entry included in WM hkcu/control panel/backlight/QKeyLedTimeout - Rose definitely doesn't
3. The issue could be a case of WM 6.1 limitation - Rose has in fact three keyboard backlight arrays with separate light managements (soft keys, numeric, QWERTY - try to use them simultaneusly and you will see - their timing is independent on each other) and I've found some extra HTC registry entries concerning power management confirming a bit non-standard settings. Unluckily, nothing useful there for the kb backlights.
Sorry, based on my experiments, I can advice you only one very strange way how to overcome it for now: Limit the display timeout to the same 10 seconds as the keyboard has. At least, first press of any key will become inactive and just light-up both display and keyboard. Until display works, all keys are still active even the keybord backlight is off.
Nevertheless, any opposite finding will be appreciated...
Thank you for your investigation
I have a new s743 and this is the exact problem I came searching for fix for!
Too bad - it really is a sweet phone.
-John
To me this is a winmo thing. I don't understand why this option isn't included from the factory. It is a plain "NO BRAINER"! It's been this way on all my previous devices whether pro or standard. The diff being the pro os has wonderful tweaks and various cabs one can install to set the time out. What we need is to get some tweaking guru to set up something like ACT for standard. Problem is so little love for the standard os. The screens are to small anyway for my taste. I'll just stick to pro, the tweaks are better.
Well, i set the display timeout on my device to 5 seconds. Backlight of the qwerty and numeric keypads went off after 5 seconds.
The softkeys remained lit till 10 seconds was up.
my atom pure's touchscreen is totally not functioning. tried to upgrade different roms but still no help. so i buy a touchscreen replacement and send it to somebody who can fit it on. the touchscreen replacement fits well but the problem is when im on the screen alignment program, point tapping dont end!! i meant the alignment process never ends. i installed a registry editor so that i can edit the touch settings value. but since the screen is not aligned cant use the virtual keyboad to input the necessary value. so i need the help of chefs here to apply my idea. is it posibble to cooked the correct alignment value on rom and at the same time skipping the alignment screen after a had reset just like what we have on some of hermes rom? if this proceedure is already implemented please send me a link of that rom so that i could try it coz i have a feeling that it will solve my problem.
thanks a lot more power
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!!
Searching through the Internet for the possible solution regarding "Wake Up from Standby" problem i came across this Article.
The suggested solution for users facing this problem was to deselect the "Auto Adjust Backlight" option from the Power settings menu.
The suggested solution for Kitchen Chefs was to use another Power Application in their Kitchen.
I think that this could be useful for all of us.
for the wake issue, try this it should work :
1) take the flesh.bin, the ACER_EUU and the extrom.bin, from arto's rom,
2) then take the original acer 3.003c and extract the .exe file in a folder with winrar or sevenzip
3) dump the .amf file from it with the toolbyamper
4) now delete from the original acer rom those files: flesh.bin, extrom.bin, ACER_EUU, toolbyamper and the .amf file
5) put the flesh.bin, extrom and ACER_EUU that you take from arto's rom and put it in the acer v3 folder...
here you go !
jeje too complicated this last solution...
i tried solution mentioned by brianmaster and it works...
regrats
How to make what the device with SRS WOW HD 1.5.1.0 woke up?
How it has made Arto in the rom?
I wish to instal RU rom, but srs hd wow only on Arto rom works without a dream!
Sorry my bad English
You must uninstall SRS WOW HD 1.5.1.0, this driver is only for HTC
So on Arto rom works srs wow hd! Also does not sleep!
I even took srs wow hd from Arto rom, all the same on others rom does not work!
SRS WOW HD works only on Sense ROMs like Arto's.
right now use Arto rom, but it would be desirable to put RU rom and to fasten srs wow hd, but ways I so understand was not present (
Wake up solution?
brainmaster said:
Searching through the Internet for the possible solution regarding "Wake Up from Standby" problem i came across this Article.
The suggested solution for users facing this problem was to deselect the "Auto Adjust Backlight" option from the Power settings menu.
The suggested solution for Kitchen Chefs was to use another Power Application in their Kitchen.
I think that this could be useful for all of us.
Click to expand...
Click to collapse
I think that the wake up issue is caused by a conflict between windows and acer relating to the < End Key > fuction.
I've tried this for a day and it works for me:
Of corse uncheck < Auto adjust backlight by battery level>!
preferences-phone-check wake up from sleep
preferences-End Key-choose lock and suspend( hold to suspend)
Settings-System-backlight-battery tab-check both boxes
Settings-System-backlight-external power tab-check both boxes
Settings-personal-buttons-button 2 choose <Today >from menu on the bootom
TO WAKE UP PHONE: PRESS ( < ) button at bottom of device.
This W\Official acer ROM( don't know about settings in cooked ROM)
Also:< SRS-WOW HD> works beatifully on stock Rom
1.Installed SDK certs., .net config.3.5 Then:
2.Install SRS-WOW HD to device ( afer installation finishes *SOFT RESET*)
3.after reset go to settings-Sys-srs wow icon open and make personal adjustments.
Hoping this works for all!
arghh !! I'm still having wake up issue either I'm using v3 flashing tools...damm !!! I have this !
I've went back to Arto's ROM wich hasn't got the wake up issue. But when i used active sync it did again. I disabeld the active sync and then I was perfect again.
So maybe active sync has something to do with it to?
****inglogins said:
I've went back to Arto's ROM wich hasn't got the wake up issue. But when i used active sync it did again. I disabeld the active sync and then I was perfect again.
So maybe active sync has something to do with it to?
Click to expand...
Click to collapse
Did you had some issues with my Modular ROM? If you share it with me, maybe i can make improvements.
Yes, I've treid your modules Rom and really loved it. Unfortunatly I had the wake up issue (i reported it in your tread and you also fixed me a cab for dutch language realley fast
In arto's ROM I don't have the problem unless active sync is on push (or other polling, haven 't tried) no mather wat setting I use for backlight or wake up when a hardkey is pressed.
I think you have to contact Arto because he problely has the solution (since his Roms don't have it......
****inglogins said:
Yes, I've treid your modules Rom and really loved it. Unfortunatly I had the wake up issue (i reported it in your tread and you also fixed me a cab for dutch language realley fast
In arto's ROM I don't have the problem unless active sync is on push (or other polling, haven 't tried) no mather wat setting I use for backlight or wake up when a hardkey is pressed.
I think you have to contact Arto because he problely has the solution (since his Roms don't have it......
Click to expand...
Click to collapse
Well, i am using the Geek Rom since i cooked it, and don´t have any wake up issues.
That is strange then...... Maybe I'll flash your rom again sometime but i'm pretty satisfied with arto's rom so far.
I'll let you know by time
****inglogins said:
That is strange then...... Maybe I'll flash your rom again sometime but i'm pretty satisfied with arto's rom so far.
I'll let you know by time
Click to expand...
Click to collapse
No problem. Arto also makes very good ROMs.
3.003 drivers were supposed to fix the wakeup problem, but it seems there are certain options/customizations that still can create the wakeup problem.
For example, I have had wake up issues on all the ROMs I've tried (Rafyvitto's, Arto's and UFE's).
I have disabled backlight based on light levels and the problem occurs much less often. Currently trying the extended version posted a little earlier (using Acer Preferences, so any key can wakeup from standby, etc.)
I do use activesync to sync with my computer; I do download push mail (from gmail); I do use swype; I automatically download weather info - on any ROM I use... so it is possible that either of these is the culprit...
/Sifaan
In two weeks i didn't have one wake up issue with my ROM.
Autobacklight is on, i don't use the end call button for sleep mode. I just press the power button and S2U2 locks the device.
And i deativated the option to turn the backlight of if the device is not used for 30 seconds.
Possible reason for wake up problem
I am nearly sure that wake up issue occurs when i change something in windows folder. Especially when i change lockscreen, use some programs related to device lock and change start menu icons etc., wake up problem occurs every time regardless of rom (i have used nearly all custom roms)
Hello,
the last 2 times that i had this wakeup issue, the story was the following:
-i received a text
-i went in my incoming box and looked for the message
- next i closed the incoming box by pressing the end key
- screen turned off 1 minute later
and so no way to wakeup my phone !!
Hope it could help, bye.
Hi all, I am wondering if anyone knows how I can disable the touch capacitive buttons on the flyer/view.
I use my tablet in landscape a lot, and end up using the bezel as a handle and then hit the buttons, I am running DextersJB14 rom with the patch.
Any help would be appreciated.
Hm, strange enough, at the moment I use DextersJB16 and these buttons are not active. I used 14, 13 and 12 and cannot even remember the buttons were active... Did you look through dev settings?
i believe he is running mobileUI edition and i activated buttons here, and a fault in the wifi build.prop also enables the softnav buttons.
if the build.prop is modified , the hardware buttons remain active (as many requested for mobileUI) and softbuttons goes away.
it will be fixed so softbuttons are gone in next update, hardware buttons remain active in mobileUI
PabloFiasko said:
Hm, strange enough, at the moment I use DextersJB16 and these buttons are not active. I used 14, 13 and 12 and cannot even remember the buttons were active... Did you look through dev settings?
Click to expand...
Click to collapse
Interestingly enough, the buttons are not lit, but do respond. I didn't see any settings that appeared to be able to change this. Might be nice to make this a toggle setting in the future, though I don't know what that would entail for Dexter. I suppose I could try out 16, didn't realize it was out.