Related
I wanna make another post here cause in the last post this issue wasnt resolved and i wanna fresh thread here, please only post if you have the solution, thanks hope theres someOne who can get this issue resolved.
Do you use AutoKeylock ?
I had this problem when I started using 6.1 ROMs first.
In my case I had about 6 applications I always installed right off the bat after a new ROM flash. One of those was Maniac's AutoKeylock.
I timed the duration between answering a call and having the call go white one day, and it seemed to me to match precisely with the screen timeout settings I had in AutoKeylock.
I removed the application, and have never seen the problem happen again.
However, I do miss having AutoKeylock.
I realize that this could be totally coincidental, and thus I asked before whether others who had the problem also used AutoKeylock but never got a reply.
Perhaps you can reply as to whether you use it or not. And, if you do, whether removing the application resolves the issue for you.
If there is a correlation then we can alert Maniac to the issue, and he may be able to find a solution.
LiverpoolFCfan said:
I had this problem when I started using 6.1 ROMs first.
In my case I had about 6 applications I always installed right off the bat after a new ROM flash. One of those was Maniac's AutoKeylock.
I timed the duration between answering a call and having the call go white one day, and it seemed to me to match precisely with the screen timeout settings I had in AutoKeylock.
I removed the application, and have never seen the problem happen again.
However, I do miss having AutoKeylock.
I realize that this could be totally coincidental, and thus I asked before whether others who had the problem also used AutoKeylock but never got a reply.
Perhaps you can reply as to whether you use it or not. And, if you do, whether removing the application resolves the issue for you.
If there is a correlation then we can alert Maniac to the issue, and he may be able to find a solution.
Click to expand...
Click to collapse
You know if the reason you miss autokeylock is for the ability to set a time for the screen to turn off and the keypad to lock, smarttoolkit does that, with no problems.
HTCP4000PPC said:
I wanna make another post here cause in the last post this issue wasnt resolved and i wanna fresh thread here, please only post if you have the solution, thanks hope theres someOne who can get this issue resolved.
Click to expand...
Click to collapse
How often it happen?
With my phone running Kavanas I will get a white screen once after a reboot and then I press and button and it goes back to normal and wont do it again. I have gotten used to it.
For some reason I think it has to do with Tornado PowerControl, do you have that installed? I just cant figure it out exactly. Maybe we can find a solution.
We'll i believe this White screen has something to do with the backlight settings in power managment, i find if you leave screen on full and turn off the phone from turning off the screen, the white screen wont happen, this isnt so bad, cause if u want the screen to go off just hold down the disconnect phone button, not too bad cause when your not wanting to use the phone anymore the screen still goes off, also you can turn the backlight off in accessories which is the same as setting the screen to go off automatically in 5 seconds, white screen fixed moreless.
Same issue with Ricky's v24 and now with Rose 1.7
I also am experiencing this issue, but do not have installed neither Maniac's AutoKeylock nor Tornado PowerControl.
It happens sometimes during a call, sometimes not.
It happens when leaving the phone unlocked and timesout idle time. If hit the Home or back buttons, it shows the home screen again and next timeout does work fine.
I have beeing looking up and down for fixes but was unable to find one. Some say turning off "Run Lowlight" JOGGR setting, some say flash after a hard reset...
It seems that running lowlight (joggrinfo.exe -m -t) helps a bit. If the phone is fully bright and rests on the table, the screen goes white after timeout.
However, if run lowlight and let it alone, it turns off the screen normally.
Also when it goes white and hit back or home button, the screen goes mid-bright, and then turns off normally.
However, when unlocking, it goes full bright, and then the issue comes back.
In summary ...
Full Bright -> Times out to whitescreen.
Mid Bright -> Times out to lights off.
Unlock -> Goes full bright -> Times out to whitescreen.
White screen -> Hit Back/Home button goes mid-bright -> Times out to lights off.
It would be great if lowlight could be run when unlocking the device.
Does it work same way for you guys??
Regards.
This will stop White Screen from happening.
ok this is a way to avoid the white screen issue, (Click on Light Config) then open CeleTask and in CeleTask - Tools use Close Screen this will turn off your screen and allow the backlight from turning on when screen turns back on, also remember u need to set your power settings to (Backlight time out on battery 5 Seconds and Backlight on AC can be 1 minute which u never use) and Display time out Never..)
You can also use CeleTask to disable the screen when you make a call, just open CeleTesk when you hit call.
Topic should be changed as not a fix but work around "sortof":
Process of illimination:
My recomendation would be try a hard-reset, don't install any programs see if that fixes it now when installing programs don't bung them all on install 1 @ a time soft-reset give it while see if problem resumes, do this for all software then you may find the culprit?
This is not an issue faced by all so something has to be the culprit.
Bad Flash?
Software Install?
JOGGR?
Power Settings?
They are just examples.
I had this happen once but on WM6 and a hard-reset was what was needed and didn't pop up again........
HTCP4000PPC said:
ok this is a way to avoid the white screen issue, (Click on Light Config) then open CeleTask and in CeleTask - Tools use Close Screen this will turn off your screen and allow the backlight from turning on when screen turns back on, also remember u need to set your power settings to (Backlight time out on battery 5 Seconds and Backlight on AC can be 1 minute which u never use) and Display time out Never..)
You can also use CeleTask to disable the screen when you make a call, just open CeleTesk when you hit call.
Click to expand...
Click to collapse
These instructions have fixed my device... I got an Elf and I made it my primary phone, and now I´m experiencing new ROM´s in my S621. This problem happens in my device (the S621, of course), and I´m now using NRG remade by Ricky and Stylez, and this problem with the screen seems to be solved with this tip.
This problem does not happen when I use "Kavana remade by Ricky and Stylez" only with NRG and it´s Remake.
Regards
If this isnt helping try just disabling Timeout and set everything else ur way u want.
One thing I really liked about my T2 out of the box was the fact that receiving a text message did NOT wake up the phone.
All of the sudden, it is waking up with every text. I checked to make sure that somehow DisableSMSWakeupEvent hadn't been changed to '0', but it is still set to '1'. Did a soft reset, rechecked the registry value (it's still set to '1')but the phone continues to wake up with every text. I also checked in event notifications to make sure I hadn't inadvertently checked the 'Display message on screen' box.
I had installed Advanced Configuration Tool a few days ago, but uninstalled it the next day after only checking out the options and didn't change anything with it. My only other recently installed software is SPB Time, but it's been in place for more than two weeks so I don't think that's doing it. And I'm *still* using the stock AT&T rom.
What gives? I don't want my phone to wake up when I receive a text!
I only fixed this when I used advance config to tell it to wake up on text, softreset, don't wake up on text, soft reset, and then it finally worked how I wanted it.
try deleting the string and then recreating the dword string. and then soft resetting.
i dont understand why you dont like your pro2 to wake up when the SMS comes in, how will you know a message has arrived????
this is a must feature of a phone,each person who are involved in thw world's business will require.
Hope you are not a spooky person,
nokiadashi said:
i dont understand why you dont like your pro2 to wake up when the SMS comes in, how will you know a message has arrived????
this is a must feature of a phone,each person who are involved in thw world's business will require.
Hope you are not a spooky person,
Click to expand...
Click to collapse
It will still vibrate, beep etc, just not turn on the screen until you press the button.
Mine is doing the same. I agree with the OP
Why?
Because my phone lives in my pocket, and when I'm seeing patients or have my hand somewhere you probably don't wanna know about, I can't check every text as it comes in. If the screen turns on in my pocket, then I begin pocket dialing or other bad things. And THAT'S why I con't want my phone to light up when I get a text.
Besides, I have the LED set to flash with new message notification, as well as to vibe so I'll know I just got a text.
The good news is that after the problem has suddenly disappeared just as suddenly as it appeared. Guess I must have bowed down properly to the phone gods in my sleep last night...
You could try using S2U2...
That way you won't start 'pocket dialing'.
Bright.Light said:
You could try using S2U2...
That way you won't start 'pocket dialing'.
Click to expand...
Click to collapse
+1 for S2U2 Pocket dialing is a thing of the past... I dont know why microsoft or HTC havent incorporated a better lock
jlmwrite said:
One thing I really liked about my T2 out of the box was the fact that receiving a text message did NOT wake up the phone.
All of the sudden, it is waking up with every text. I checked to make sure that somehow DisableSMSWakeupEvent hadn't been changed to '0', but it is still set to '1'. Did a soft reset, rechecked the registry value (it's still set to '1')but the phone continues to wake up with every text. I also checked in event notifications to make sure I hadn't inadvertently checked the 'Display message on screen' box.
I had installed Advanced Configuration Tool a few days ago, but uninstalled it the next day after only checking out the options and didn't change anything with it. My only other recently installed software is SPB Time, but it's been in place for more than two weeks so I don't think that's doing it. And I'm *still* using the stock AT&T rom.
What gives? I don't want my phone to wake up when I receive a text!
Click to expand...
Click to collapse
I do want my Tilt to wake up with every text and it isn't. I am new to this, can you tell me how to make this change?
Hey fellas, to lock my phone I use the pattern lock, but since yesterday every time I lock the phone with power button or sleeps itself after 2 minutes, it doesn't show me the 'draw pattern screen', just the regular 'slide to unlock'.
So, I go and set the pattern up again, and lock it, it shows the 'draw pattern screen' and only shows once, after I lock the phone again, it won't appear anymore.
I'm using CM6.1.1, obviously rooted phone.
Any help or suggestions? Moderators feel free to move this post to cyanogen's thread if needed. Don't know if this might be a problem of CM itself.
Did you enable any of the quick unlock settings in Cyanogenmod settings? I bet my breakfast (which I already ate, sorry) that its because you need to review those CM settings. In User Input or something or other.
Uncheck all of those settings (that enable quick unlock)
(besides those pattern locks are easily hacked -- with the right light and the right amount of grease from your finger anyone can see your "path to unlock" - Im just sayin!)
Sorry man, that quick unlock feature is definetly not checked, it's under "settings/cyanogenmod settings/input settings", quick unlock not checked.
U owe me a pancake lol.
I dont remember getting creative with locking and unlocking settings, the weirdest thing I did was to install a few themes to the phone. Imma try putting everything to default, and start from there.
I've experienced some unlock and lock issues with cm6 aswell. It seemed as if there are settings that conflict with eachother. What happened to me was I changed it to rotory unlock with lock set to immediately engage on screen off. After changing that it wouldn't lock but the screen would turn off. I had to set it to 1 second and then reboot then it would lock just fine.
Sent from my HTC Vision using XDA App
What surprises me is that it stopped working for some reason, because I've been using cm6.1.1 for a couple of weeks and worked perfectly..
Sent from my HTC Vision using XDA App
don't remember where the setting is but it sounds like the time-out setting is not proper, the phone does not lock right away if it is sitting on the table and goes to sleep on it's own but you can set it to do that, i had mine set to 30 seconds so that if the screen turned off while i was waiting for something to download or happen i didn't have to unlock with my pin each time. look through the settings (probably security or cm settings) for the proper tweak, i would give better instructions but i'm currently on miui ROM
g_grey said:
don't remember where the setting is but it sounds like the time-out setting is not proper, the phone does not lock right away if it is sitting on the table and goes to sleep on it's own but you can set it to do that, i had mine set to 30 seconds so that if the screen turned off while i was waiting for something to download or happen i didn't have to unlock with my pin each time. look through the settings (probably security or cm settings) for the proper tweak, i would give better instructions but i'm currently on miui ROM
Click to expand...
Click to collapse
Yeah, these settings are found under CM Settings->User Interface (down at the bottom). I don't think these will be the cause though, since the OP said he didn't really mess with any of the settings. Also, I don't think the settings would cause the "Slide to Unlock" screen to appear (the phone would simply turn the screen back on to whatever was last on, no pattern unlock, no lock screen).
Have you installed any new widgets or lockscreen apps recently? Out of curiosity, have you tried any of the other lock types just to see if they do the same thing (like PIN or password).
Hello, everyone.
Well...3 days ago it was raining in my city and I was talking with the Defy on the streets, the phone fell to a puddle in the sidewalk, I just picked it up and kept talking, but then I saw there was some fog and little drops of water inside the screen, though the phone was still working perfectly. The next day the fog was still there and the phone was working, but later that day the screen just didn't turn on and the LED was always turned on in red (but I could see the screen items under high light and I managed to see something in the notificacion bar like "new electronic device recognized"). In order to remove the fog I took the battery off and put the phone under my laptop, so the low heat would vaporize the remaining water and maybe the screen would work again.
Now I have the phone with no fog but the screen is still not working, though I can turn on the phone and it vibrates when I press the capacitive keys and it sounds when someone calls and that stuff, it's just the screen isn't working, all black, like missing the retroilumination. The red LED is always on. So I thought of sending it for repairment, but I can't flash any sbf, as I didn't had USB debug mode enabled the RSD Lite says "unable to retrieve initialization values from INI file (0x7029);phone connected". Can I enable the usb debug mode via adb shell?
The phone is rooted, using JBoogie3 Blurless Honey, it's a Vodafone Spain.
TL;DR version: phone got into a puddle, screen stopped working, red LED always on, can't flash any SBF to send it to repair because usb debug mode is not enabled and can't enable it since I can't see the things that are on the screen.
I'll love for ever the one who can lead me to a solution. Thanks in advance, please help, I'm desperate.
PS: The phone was closed and the rubbers on the sides (headphones and usb) were closed too. Sorry for the long post.
i can try and guide you to the usb debug on of settings if you want
That'd be helpful, any screencaps would be awesome. I think there was no scrolling to do in Settings tab nor in applications,therefore, easier.
danirolo7 said:
That'd be helpful, any screencaps would be awesome. I think there was no scrolling to do in Settings tab nor in applications,therefore, easier.
Click to expand...
Click to collapse
first thing first can u get into the settings? if not wat launcher do u have?
GoLauncher EX..I think settings is in the right low corner when you hit menu key in the homescreen..
ok once ur in the settings press near the botton of the screen so the last selection, then turn ur screen sideways and select the last box again to go into development however this time press about 0.5 - 1cm above the botton of the screen. once you in development select get a ruler and from the top of the screen not the fone press at 1.5cm. that should then enable usb debug. if you need any more help just ask or if something does not make sense
Will try several times..but I can't lose time rebooting everytime I try, anyway I can check if debugging is enabled trough adb or something? >.<
danirolo7 said:
Will try several times..but I can't lose time rebooting everytime I try, anyway I can check if debugging is enabled trough adb or something? >.<
Click to expand...
Click to collapse
Sorry none that I no of
I've managed to flash the SBF, downloaded this RSD http://cyberwarez.googlecode.com/files/RSDLite-4.7+patch.zip and put the INI file in the root folder of RSD installation. Thanks for your help
np. glad i could help out
Well, I thought I had a fault-free HOX. I received it on Saturday and haven't really used it much because I'm waiting for screen protector and case to be delivered.
I left the phone at home today (on standby) while I went to work. I came back and as I swiped the screen lock off the screen started flashing in multi-colours whenever I touched the screen.
If I didn't touch the screen, it was fine, and soon as I touched the screen it would start flashing in different colours again.
I rebooted the phone, and same problem. I rebooted again, and the problem was gone. I haven't been able to get the problem to reoccur.
Should I return the phone for a replacement, which may or may not have additional problems, or considering the fact the problem hasn't reoccurred, do I just keep the phone?
My Guess was the 'Show Screen Updates' was Enable.
Settings >> Developer Options >> Make sure you unchecked all under 'user interface'.
You got it in one, thanks ;-)
I can replicate the effect by enabling 'Show Screen Updates'.
I think my partner must have been playing with my phone while I was out!
What is this option for?
It happens to me all the time. It's probably because you have a lot of hand sweat and when you touch the screen your sweat gets on it. Just wipe it off with your shirt or something.
Or it could just be that the "show screen updates" option is enabled lol