Hi, I tries searching for the solution to this by the "symptoms", and nothing came out, sorry to open a new thread for my own doubt but...
Whenever I make a call longer than 30 sec (which is when the screen dims down), after the call ended (either by me or the caller hanging) the screen stays dimmed down, and for some reason the everything in the Start Menu bar (except the task manager) is unresponsive through touch. The rest of my today screen still responds to touch or d pads, both on screen softkeys work. The start menu is only accessible with the default win button.
The only way I have found to correct this is by pressing the power button twice (going to standby and back). It's not a huge deal, but it is somewhat frustrating.
Any ideas or fixes?
Thanks in advance =)
EDIT: I'm using stock rom and HTC Dialer.
btw, anyone else having this issue?
I also have this issue but no solution (or i can't find the solution) till now. I think it is the bug in this ROM version so hope new ROM will solve this issue.
It´s a well known bug that has been discussed many times......
It happens when you´ve set a device password and your screen turns off during a call.
Solution 1:
Don´t set a device password
Solution 2:
When the above happens, turn the screen off and then on again (2 quick pushes on the power button) and you should be back in bussiness.
Solution 3 (the one I´m using):
if your exchange server enforces the password on your device (you can´t easily turn it off): install a small cab called StayUnlock (do a quick search, it´s either here or over at www.modaco.com), which will automatically disable your password everytime it´s enforced by your exchange server.
Thanks Michi! Step 1 did the trick, I don't need a pswd on my device anyways. XD
When your new it's hard to follow up or search and find stuff when there is SO MUCH information in here.
Thanks again =)
Related
Hi, I have discovered that Direct Push e-mail is causing the wizard to power on at certain intervals and for me at least was causing significant power drains under crossbow. Here are 2 fixes.
1. This is for those that use an exchange server and/or direct push email.
-Locking the device stops the wizard powering on and still allows use of direct push email.
2. Those that don't wish to lock their device and don't use direct push email.
-Change the following Registry values:
HKEY_CURRENT_USER\Software\Microsoft\ActiveSync\
HeartbeatIncrement DWORD: 0
InitialHeartbeat DWORD: 0
MinHeartbeat DWORD: 0
MaxHeartbeat DWORD: 0
Reset
Hopefully this will work for you guys it did for me, no power on all night.
EDIT: Sorry after longer testing No. 2 appears not to work however I still think it has something to do with Activesync and Direct Push E-mail. The settings reset themselves after soft reset.
It works!
Confirmed. Locking the device via the Today screen plug-in prevents the undesired power ups.
I am using a small program called Device Lock with the Suspend option. I set Button 4(Hold) to Device Lock. Sometimes it wakes up immediately after suspending, but I can press the power button and it stays off.
http://forum.xda-developers.com/showthread.php?t=261277
I discovered this yesterday also.
He means using the today screen plugin to lock it, not just having buttons locked except power in case you weren't aware of that.
No wonder I never had this problem. I use batterystatus to lock my screen all the time. Isn't the lock nice? Very convinent. My only hope is if there is anyway to unlock it with one hard button.
Oh. I was using the Lock in the control panel set to lock after 0 minutes of idle so when I pressed power it would power down and lock.
I'll have to find a better way to lock.
it didnt work....
Malik05 said:
it didnt work....
Click to expand...
Click to collapse
using the batterystatus, not the lock in the control panel.
i meant the regedits, it didnt fix the problem...i dont like to lock my phone when not in my pocket...
i hit the lock button on the today screen and i watch it turn on and off every minute... still... it didn't help ...
I wonder how did faria fix it in his ROM.
any update? wokring solution ?
Faria has the only known solution to this but is refusing to share that knowledge by looks of things, maybe so he can forces users to use his own cooked ROM or something...
the only working solution i have seen was the one rusigor suggested and that was taking the device password off. and im believer because it worked for me. so im sticking with that. Also i noticed that my battery is lasting like alot lot lot lot lot lot lot longer now. before i would go to bed with the phone at 80% battery and when i would wake up it would be like at 30. The last couple nights i would go to bed with it at 59 and woke up and it was at 55. I was shocked. so thats why im sticking with this method.
neonkoala said:
Faria has the only known solution to this but is refusing to share that knowledge by looks of things, maybe so he can forces users to use his own cooked ROM or something...
Click to expand...
Click to collapse
I hope it's just a case of him not knowing of this thread! Has anyone PM'd him?
I will if no one has yet.
Karl
Sorry meant to update this, fix has been around for a little while now.
Untick Turn off backlight for both battery and mains power and this will cure the problem however you may still have automatic power offs.
I don't use push, nor do I have an Exchange server configured. I also had a problem with automatic power-ups. I found that having the device configured to display the owner info screen when it is switched on caused it to power up on its own shortly after it was switched off.
Getting rid of the owner info display on power-up did the trick for me.
I'd love to know how those two things are connected.
I found a solution for me
I also think is more related with the screen light as I used the WM6 MB and i put the screen auto off after 30 sec, and it was waking up very frequently. I completly removed the screen light auto off and now my phone never wakes up alone (just when it should be =D).
Hope it helps!
Hey,
I've noticed that after a call the start bar freezes? I can't access it using the hard button or even the touch button.
Has anyone got a fix for this?
Thanks
A short press on thepower button to turn the screen off and another to turn it on again will fix your problem. This has been discusssed previously and the cause is a bug in the HTC ROM when your device is password protectd.
Either turn off your password, or if it has been forced on by your company´s exchange server you can look for a little app called "stayunlock" I believe, which will effectivly prevent the exchange server from enforcing the password.
Don´t have the link handy right now, but this app is floating around somewhere either here or on www.modaco.com
Hope it helps!
Thanks
I think i'll still get a brand new phone from t-mobile hehe... hopefully once the kitchen opens we'll get super roms..!
Hello,
I just received my new Kaiser two days ago and I have a problem with the phone application.
Whenever I'm on a call and the screen backlight turns off, after the call the Start button and some of the "upper menu" buttons stop working and the backlight never turns on again. To fix this problem I have to press the power button to turn off the device and turn it on again.
Any ideas?
This has been discussed several times here. It is a bug in the HTC ROM caused by the password protection of the device.
Workaround: either the one that you already discovered yourself, or disable the password.
If you can´t disable the password because it is forced on by your company´s exchange server, there´s is a small utility called "StayUnlock" which disables the lock for you.
Just do a simple search - it´s either here or on www.modaco.com
Worked!!! Thanks a lot... I'm now using Pocket Secure for password protection...
I have no problem with company exchange servers yet i can't seem to find the way to delete the password. help pls. tks
Hey guys,
Right, I've come over from symbian, namely UIQ and the SE P-series, so am used to things being somewhat different. The main issue I don't seem to be able to find a solution to is the screen locking problem.
Essentially, at the moment I push the power button to lock the device, as well as enter a power save mode. I have to say, I like the way that works. However, when I recieve a call (or text with the reg fix) the phone comes to life, great, but say I miss the call, or the phone is in my pocket, the screen is now ACTIVE. Not good news.
How am I supposed to lock this device properly? Screen lock and then the power button? Can't I get a simple tap on the power button to lock and power save the device?
Essentially, if I have a missed call or message I just want the phone to vibrate once, then keep an LED flashing intermittently. But I want the screen to stay LOCKED.
Any help would be much appreciated, and thanks for all the other useful tips on the forum!
Cheers,
Daz.
Go start/settings/System/Long Press End Key
Select automatically execute etc
and Lock device
then OK
then, a long press on the hang up button (bottom right) will lock the phone.
Hope that helps
Perhaps I didn't explain myself. I know how to lock the phone, but how do I make use of the power button tap mode? In other words, the power saving mode?
Can I set up a button that locks the phone, AND sends it to power save mode? (or "turn it off" as WM seems to call it).
Thanks again,
Daz.
I found a regedit in:
HKLM\Software\HTC\KeyLock\SameAsDeviceLock
Set it to 1, but it doesn't do the trick. In fact, it now causes the power button click to not lock the keys.
I suppose the only option is to have standby mode come on after a timeout, lock the device, then it will go into standby on its own. Seems like a slight waste of battery to me!
Cheers,
Daz.
I really want this to work too,
It should unlock and turn on when recieving a call, it should just turn on when recieving an sms (so you can have a quick look from who it is, and then unlock to reply)
and when you lock the device it should automatically turn off...
Not EXACTLY what you want, but S2U2 in the "Development and Hacking" section will improve matters for you.
When you turn the phone off with the power button, S2U2 kicks in. Then:
1) If you turn the phone back on, you'll get the slide to unlock screen.
2) If a call comes in, the phone turns on and you see the caller ID (with full screen picture, if you so desire) on a "slide to answer" screen. The S2U2 default settings ensure that the phone turns itself back off again if you fail to answer it.
3) If a text / e-mail / mms comes through, it notifies you but remains off... When you hit the power button, the "slide to unlock" screen will show missed calls, text messages, e-mails (and even the weather if you want...).
Check it out, it's an essential piece of software in my opinion... http://forum.xda-developers.com/showthread.php?t=381588
Thanks sub69, great recommendation. However, does anyone else get the bug when hitting the "x" in other applications to close them, the status bar (Or task bar) goes all scrambled and looks like the S2U2 status bar.
Shame this isn't built in though, would be nicer to see the TF3D interface rather than a 3rd party one.
Thanks again!
Daz.
Anyone with other suggestions? S2U2 is just a little too buggy at the moment on the diamond...
use "BatteryStatus" from www.chti-tai.info, they have a option for devicelock on wakeup, so even u missed a call, and the screen light up, it is still locked.
somone posted this on other thread.
--------------------------------------------------------------------------------
Now we don't need any devicelock software with diamond.
If you want automatic lock your diamond you have to change this registry key HKEY_CURRENT_USER\ControlPanel\BackLight\AutoDevic eLockEnable from 0 to 1 and everytime your backlight goes off automatically your device are locked
Sorry for may bad english but i'm italian.
Ciao
Thanks for that reg fix, seems like a good option. There was a new S2U2 version release, 1.5, and that seems to work well for me. Will see how that goes for now...
Cheers guys! Daz.
the reg edit is good, but it doesn't solve the problem of unlocked touchscreen prone to being pressed during incoming call (when scrambling in your pocket to take out the phone)
btw there are several other threads where this problem is addressed and deeply analyzed (without a complete working solution, however...)
dazbradbury take a look at sensorlock, if you have not already.
Okay, I'm having an odd one and searching around here for about three hours yielded me nothing, so I'm going to lay it down here:
The keylock on my Diamond fails to function at all. I've got the New SwiftBL Diamond ROM 6.0 installed since yesterday, and I think that is also when this started. I will also post this in the ROM's topic.
I checked the following settings:
- Settings, Long Press End Key is set to Automatically Execute: Lock Devie
- Settings, Key Lock is set to Lock all buttons except Power button.
I get no error messages, the only thing I see when holding the End Key is a short flicker of the screen, after which the Home Screen comes up. Do note that the keys are not appropriately locked.
I do not wish to use S2U2, and I am wondering why locking my device does not work. Anyone having any ideas?
you get this is you put a pin or password to protect your diamond and use one of the cooked roms, most roms have this bug now and i'm yet to find a fix other then to remove the password/pin completly
yeah, i have had this issue, its the rom. just let swiftblade know and wait for the next release
Able to lock (with issue)
Hi, I agree this is a bug. I configured my exchange account and have the lock policy enforced by my server. With the stock ROM there was no problem at all. But after the upgrade to the RUU_Diamond_HTC_WWE_2.03.405.3_Radio_Signed_Diamond_52.51.25.26_1.09.25.23_Ship ROM, the Long Press End Key no longer works to lock the device (the screen flicks).
I found a **workaround** (but not solution ). Long press the end key (as you normally would) and wait for the screen flick, press the power button (it have to be the first key touched after the screen flick). That's all, the device should be locked now.