Database Info

Preventing accidental button pressing

Hi,
I've got a problem with my Trinity, where if it rings and I pull it out of my pocket, sometimes one of the buttons gets pushed as it rubs past the material, so either the call can be hung up on or it gets answered before I can see who's calling.
I also get a similar problem if a calendar alarm goes off, or if there is a text message. Sometimes these can be dismissed before I get a chance to see what is causing the notification.
I guess this is a problem on many PPC phones which dont have a cover. Does anyone else experience this?
Does anyone know of any way to solve this? Perhaps having a secondary lock button which needs to be pressed before the hard buttons become active or something like that...?
I guess it would need some software installed, as I havent found any way to do this through the normal settings.
Thanks for any suggestions!
Cheers,
Ben

My Jasjam comes with a screen lock. Once this is activated you first need to press the unlock button which gets assigned to the left soft key followed by another button on the screen. Quite effective I would say.
Regards

srmz said:
My Jasjam comes with a screen lock. Once this is activated you first need to press the unlock button which gets assigned to the left soft key followed by another button on the screen. Quite effective I would say.
Regards
Click to expand...
Click to collapse
Hi,
Is this the same as the "Device Lock"?
My phone has this too, but it doesn't work for when there is an incoming call...ie you dont have to unlock the phone first to press the green "handset" button.
Ben

Hi Ben,
I have been having the same issue as you with my Jasjam. I tried using a hard case which was just too bulky and annoying, so I've since used something like those iPod socks and just keep it in my pocket. I just take extra care when pulling it out so it doesn't knock the green answer key. I think this is just something we're just going to have to get used to unfortunately.

Touch Cruise Backlight Problem

When I am on a call the backlight on my Touch Cruise turns off - I don't mind this. The problem is that when I try to turn it back on it is extremely dim (even if the backlight setting is "bright") and I need to use "Adjust backlight" to make it brighter. In sunlight this is almost impossible to do since I cannot read the screen. Even after I readjust the brightness, whenever the backlight turns off and I turn it back on, the backlight is dim again.
I have tried renaming the \HKCU\ControlPanel\Backlight\LockLevel folder to LockLevelx - this has not worked.
I have tried setting \HK:M\Drivers\Builtin\RIL\EnableFastDormantDisplayDuringCall to 0 - this has not worked.
Help please!

Do you have this problem all the time or you can see this misbehaviour just now?
I'm asking, because this could be caused by some other software you installed on your device,
which does some "things" with the backlight or some call manager like PhotoContacts etc.

This happens all the time. It does not happen after I soft reset the device until I use the phone. As soon as I use the phone the backlight turns off and is dim whenever I turn it back on.

- Are you running some "cooked" unofficial ROM?
- if you are using HTC Home, try to deactivate it, just choose some different homescreen schema but not HTCHome, make a soft-reset a try it.
- check HKEY_CURRENT_USER\ControlPanel\BackLight\LockLevel\LockLevel - this should have the value 0

- running standard ROM
- deactivating HTC Home doesn't help
- LockLevel is set to 0

This periodically happens on my device too. And it's really, really annoying. I found that one way to make it go back to 'normal' for a while is to change both lock levels (in locklevel and locklevelx to value 1) then back to level 0 (including the waiting and the soft resets) and then it seems to go back to normal again.
what seems to set it off for me is using the call history to dial a number, but this is sporadic.

Thank you Marissa and Hujer. Unfortunately both your suggestions have not worked.

I have had the same problem. What helped in my case is deleting locklevel and locklevelx from the registry and then soft reset. Worked for me!!

Thanks Tim B but that did not work either. If I soft reset my device OR delete locklevel & locklevelx and soft reset, then the backlight comes back on at the correct level of brightness....until I make and end my first telephone call - then the backlight only comes back on dim. By the way if I delete locklevel, it stays deleted until I make and end my first call - then it's in the registry (with value 0) again.

sclhtc said:
Thanks Tim B but that did not work either. If I soft reset my device OR delete locklevel & locklevelx and soft reset, then the backlight comes back on at the correct level of brightness....until I make and end my first telephone call - then the backlight only comes back on dim. By the way if I delete locklevel, it stays deleted until I make and end my first call - then it's in the registry (with value 0) again.
Click to expand...
Click to collapse
Exact same happens to me, using Bepe 64 rom. Real pain in the neck.

Possible workaround
This sounds very much like the same problem Trinity users have faced since that device was released. Try searching the Trinity Forums. There was a reg fix...something to do with "fast off" or similar.
The workaround there was, after the phone call, to press the power key to put the device into standby, and then when it wakes the next time the backlight is restored. Try that anyway.

No luck with this either.

I now have the same problem. My earlier solution (delete locklevel and locklevelx) is not working anymore. There must be someone who knows how to solve this.
I am willing to do a hard reset but then I will have the problem again that after turning the phone on when it is locked the display is not readable.
Any good solutions??

Tim B said:
I now have the same problem. My earlier solution (delete locklevel and locklevelx) is not working anymore. There must be someone who knows how to solve this.
I am willing to do a hard reset but then I will have the problem again that after turning the phone on when it is locked the display is not readable.
Any good solutions??
Click to expand...
Click to collapse
Exact same happens to me, using official rom.

I had to do a double reg edit, try this which is what I use:
[HKEY_LOCAL_MACHINE\Drivers\BuiltIn\RIL]
"EnableFastDormantDisplayDuringCall"=dword:00000000
[HKEY_CURRENT_USER\ControlPanel\Phone]
"Sleep"=dword:00000000
Reboot!

Thanks but that didn't work either.
Just to be clear I do not mind the backlight staying on, dimming or turning off during a call but when I press "Call End", the backlight dims (which I do not want) and if the backlight turns off after a call it is dim when I turn it back on (which I also do not want).

Did anyone find a solution to this?
Have tried all the things on here, and some work for a little while, but then the problem reoccurs

Wow, this is so strange. Mine comes back on at the same brightness level.
You all are experiencing the same thing as Marisa?

It is an odd problem because it seems that it occurrs all of a sudden out of the blue.
One time you make/receive a call and afterwards, even if the call was only a few seconds, you terminate it and the screen either is already dim or then dims and will stay dim unless you hit a backlight changer. Even then, if you lock the phone, or the phone dims after your prescribed time, it then stays dim. The only way to temporarily fix it is to set it to the normal level and then soft reset. It will then behave properly until the next phone call.
It is very inconvenient as if it locks while this is going on, you can hardly see to unlock it.
I have trawled the internet for hours looking for solutions to this. The Kaisertweak does not work for this on this device (don't know why!) Installed Schapps but the very tweaks I need do not appear when installed on my device.
All the registry edits don't work. In fact when I go to do them, the value is already at the recommended value anyway. Renaming locklevel seems to work sometimes for a while, but then reverts back.
I think it is more a problem of undimming than dimming. It dims when I expect it to dim, but does not light up again afterwards. The Kaiser solution of pressing the power button or d-pad to do this does not work on the Orbit.
I have a fairly non scientific feeling that it's something to do with either Shell, Pontui or Co-Pilot. I have uninstalled Shell & Pontui, but it has made no difference. Makes no difference either if HTC Home is/isn't installed/running.
Another strange thing is that when it is in its dimmed state, I only have to touch the page where the backlight slider is for the light to come back up. I don't need to touch the slider at all, it's already where it should be, 3/4 of the way up.
In fact I have done the registry tweak which is supposed to stop it dimming during calls altogether, and checked to see that it 'took' and it is still happening.
Somewhere, there must be a registry key or somesuch which controls what happens after this "temporary" dimming, which says, the call is over/the device is unlocked - go back to prescribed brightness. But I can't find it.
This is a really insidious problem which drives you mad, especially when you are out and working, you don't have time for this nonsense. If all else fails in a week or so I will try a hard reset, i just don't have time right now.
Any help gratefully received.

I have just emailed O2 with this problem. Let's see when/if they reply.

[Q] Black Screen on Wakeup?

I just started having this "bug" yesterday. Basically, what happens (randomly) is that when I press the power button, remove the stylus, or slide the phone open to wake it up I'll be met with a black/blank screen. The backlighting will be on, and the phone is responsive (can receive messages, make calls, sounds/notifications work), but I won't be able to use the screen. If I use the power button to turn the screen back off and wait a few seconds, the screen might start working again. This is completely random and I cannot duplicate it with any guaranteed process, but it seems to be when the phone is waking up from standby. After a soft reset, probably half of the time I'll be met with this same delima, which leads me to believe it's hardware and not completely software.
At the same time the phone is also struggling to re-paint the screen from the change of Landscape-to-Portrait and visa versa. Also opening and closing windows to get back to the today screen also cause a problem. I've disabled TF3D to see if that makes a difference, it doesn't. I have a blank today screen with no plugins to free up the system resources, and am still having this issue.
I'm using JD's Rom (probably around 1.3, it's been running fine with no issues up to this point).
I'm also using S2U2 1.35 (if that makes any difference, haven't had any problems until recently)
The phone has never been dropped, it's in InvisibleShield, and normally sits on my desk charging all day.
This started happening last night for no apparent reason and it's really starting to irratate me.
Any advice is appreciated. Thanks.

Re the black screen:
Sounds like its software related. For example, I sometimes have this if I leave PocketTwit in the foreground and turn off phone. What software did you install yesterday? Also, do you try to press the home key and see if that clears the screen?

After more testing..
After some more fiddling around with the phone I'm about 90% certain it's a hardware issue. I noticed that when I slide the keyboard out if the slide portion is past the number line then the screen will stay on, but not update. I don't know how well I can explain it. If I'm typing and hold the screen to keep it from opening all the way then I can see the letters/words appear (in txt msg/email), but if I let the screen goes and it slides all the way open then the screen will stay on and only show what has already happened, any more typed characters will not appear, but if I move the screen back to the number row then the screen will re-draw and update what has happened.
Is this something that Sprint should fix no questions asked?

lulugirl896 said:
Re the black screen:
Sounds like its software related. For example, I sometimes have this if I leave PocketTwit in the foreground and turn off phone. What software did you install yesterday? Also, do you try to press the home key and see if that clears the screen?
Click to expand...
Click to collapse
The last piece of software I installed was Gyrator 2 on Friday-ish. Thinking that it was the problem, I removed it using MemMaid. I'm going to give the phone a flash tonight and see if it is software related (hoping for the easy fix) but as the post above says, I'm almost certain it's a hardware issue. I just wish I knew how it happened. . . So much for that time putting those InvShld on.

Final Update (this can be closed)
I took it into a Sprint store and they replaced the "flip" on the top for free (I have insurance).
Point of the story/thread, this can be closed, it was a hardware issue, and now it's fixed.

TP2 locks for no apparent reason??

I do not have auto lock turned on. I did load the VZW "clean up" cab. I can't figure out why sometime when I pick up the phone the lock is on, and other times the screen is simply turned off. I never hit lock, simply turn off screen or let it go off automatically.
Anyone have an idea?
Thanks.

Are you sure you are not hitting the top button accidentally. That button will turn off the screen.

I do use the top button. It only turns off the screen though, not locks the device. I can use it, then hit it again minutes later and the device is fine. But sometimes I'll put the phone down or aside for a while, and when I pick it up to answer a call or something I'll find it has locked itself and I have to press the soft keys.

hmm... sounds strange, I gotta go with what the 2nd guy said, I will sometimes lock the device myself (the soft key for it is on the home screen after all and it's VERY sensitive). About the screen turning off, you sure it's not just going into it's timed sleep/standby mode?

hopefully this will be of some help...i too had this problem and then i realized what the cause of MY problem was...whenever i would receive a phone call and would let it go to voicemail, when i would wake the phone back up it would be locked...i cant remember if the same thing happened when i answered the call but i know for sure it would do it when i pressed ignore call or mute ringer and let it go to voicemail...SOLUTION:i downloaded a cab called disable auto lock (or sumthing like that) and it fixed the problem...hopefully that helps..

mwrood said:
hopefully this will be of some help...i too had this problem and then i realized what the cause of MY problem was...whenever i would receive a phone call and would let it go to voicemail, when i would wake the phone back up it would be locked...i cant remember if the same thing happened when i answered the call but i know for sure it would do it when i pressed ignore call or mute ringer and let it go to voicemail...SOLUTION:i downloaded a cab called disable auto lock (or sumthing like that) and it fixed the problem...hopefully that helps..
Click to expand...
Click to collapse
I've been trying to figure this out as well and came to the same conclusion. My screen is off, I answer a call, and when I hangup my screen is locked. I did a quick google search for disable auto lock and didn't have much luck. Can you post the name of the file and where you got it? Thanks

Not sure where I found it, I think PCGeeks, but it was called Disable_Auto_device_lock.cab
HOWEVER...it did not work for me. I may have to cold reboot (from scratch) as I've tried so many different cabs, things are getting messed up. I'm trying to hold off for the ROM update.

The phone will automatically lock if you miss a call. Sometimes if you pick up on the last ring the phone will consider it a missed call and still lock the phone. That has happened on my 6700, my 6800 and now my TP2, but this is the first phone that locks after a missed call. I actually like it becuase since I dont have a S2U2 or 6.5 on the phone it prevents butt dialing if I leave my phone in my pocket or soemthing.

I have noticed the same issue. I also noticed that it did not happen before I had installed the clean up cab. I had thought that the lock button was being hit while the phone was in my pocket.

Although the "Disable auto..." didn't work for me, I down loaded and am trying S2U2. So far, and if I'm not mistake, It did not lock me after a missed call, or answering a call.
I'm going to play with it for a while. Had something similar before on my old Q9c so if it works, great!
I just hope all these friggin cabs work when I update to 6.5, or I may not! The only real pet peeve I have about the TP2 is earpiece volume. If the cab volume booster doesn't work, I won't upgdate!

I have this issue as well. It seems to lock if the person that calls me hangs up before I do. It also locks if I ignore a call. I have had it lock in the middle of a call as well. Really annoying if I need to use the onscreen keyboard to enter information during the call.
I hope someone can find a solution for this. So far, it's my only complaint about this phone.

Well, I've been using S2U2 now for a couple of days. Getting to like it! My screen no longer locks, and I kind of like the Iphone type unlock. When a call comes in 2 nice large buttons for either answer, or end (ignore).
You may want to try it.

Mine does the occasional random lock also and when it does, it wants a password that does not exist. IF anyone knows what the standard password is, please let me know. I don't have one set and need to reboot when this happens. Really my only beef with the phone which hopefully gets fixed in 6.5

I have found that if I receive an SMS the screen will come on on its own. In those circumstances I have seen it lock the screen afterwards.
I am thinking it is a failsafe put into the phone for accidental button hits after the phone wakes up from certain activity but could be in a pocket.

KforTouchPro problems.....

Hey guys, i've got a problem. First off, KforTouchPro works fine on my HTC Touch Pro, i can configure buttons fine for Morphgear, PocketGBA, SmartGear etc, it works wonderful. And as everyone that uses this app already knows, you have to switch the setting to MS IME before you launch your game emulator, or else you can't configure the keys. Well, my problem is, after i'm done playing a game, sometimes I forget to switch the setting back to default, and whenever i do a reset or shutoff my phone, it hangs at the screen right before it shows your homescreen and touchflo3d tabs.
Basically, for those that use EnergyROM, it hangs at the screen that shows you the black & blue background with the word EnergyROM 3.0 in the bottom left (or something like that, can't remember). That means you can't do anything at all, since there are no buttons etc for you to press as the home screen is not fully loaded, so basically you got a semi-bricked phone as no matter how many times i try to turn on the phone, it just hangs there, which results in me having to do a hard reset in the end.
To prevent this, you MUST restore the KforTouchPro setting back to the default setting, but sometimes ppl forget and this will cause a semi-bricked phone, which is very risky and quite dangerous.
So, is anyone else having the same problem as me?? Is there a solution to this??
And lastly, what's the difference between KforTouchPro and KforRaphael??