Related
Hi All,
Does anyone know how to get this working on our beloved HD's? I hate the way the screen goes completely black during a call, we can't use the light sensor to tell the phone that the call has finished and it is away from your ear (so screen comes back on a la iphone), and i keep doing things during a call with my ear!!
So this seems like the ideal solution - but i can't get it to work!!
I've copied over the file to the windows folder, then soft reset. Changed the registry entry for phoneLockEnable to 1 in HKLM/Software/HTC/Phone but still no joy!
All help would be greatly appreciated.
Regards
DF
hi, where you found out this software? it look's great, can you share the link to me? recall i saw some post like this, but just for diamond, i'm looking one for my hd, is there anyone have?
chanmama said:
hi, where you found out this software? it look's great, can you share the link to me? recall i saw some post like this, but just for diamond, i'm looking one for my hd, is there anyone have?
Click to expand...
Click to collapse
Sorry, i don't have the cab file, i just saw the screenshot and thought 'that's what i need'!!!
Hopefully some bright spark here can help us both (and others probably).
Regards
DF
Beside this transparent canvas, where can I get the orginal canvas?
I am using a offical ROM but I don't see this function!
I hate the way the screen goes completely black during a call, we can't use the light sensor to tell the phone that the call has finished and it is away from your ear (so screen comes back on a la iphone), and i keep doing things during a call with my ear!!
Click to expand...
Click to collapse
that's interesting, because my screen doesn't go blank during calls and it happens quite often that i accidently disconnect a call (i suppose because i hit a button with my ear).
so in search for i solution i found in Advanced config a tab Light sensor > Light sensor polling which i set enabled. the explanation says "uses light sensor to automatically turn screen off when the phone come near from your ear to answer a call". so this should set it like the i-phone does, right?
hence when i tested it, the screen still was on, even when i put my thumb onto the light-sensor.
is this because i don't have a stock rom (i use Duttys HD V1.9b XTREME) or is there something i can do about it.
it would be really nice to have the screen locked when i answer a call and to outomatically unlock it if i remove it from my head to use some function on the screen..
take55 said:
that's interesting, because my screen doesn't go blank during calls and it happens quite often that i accidently disconnect a call (i suppose because i hit a button with my ear).
so in search for i solution i found in Advanced config a tab Light sensor > Light sensor polling which i set enabled. the explanation says "uses light sensor to automatically turn screen off when the phone come near from your ear to answer a call". so this should set it like the i-phone does, right?
hence when i tested it, the screen still was on, even when i put my thumb onto the light-sensor.
is this because i don't have a stock rom (i use Duttys HD V1.9b XTREME) or is there something i can do about it.
it would be really nice to have the screen locked when i answer a call and to outomatically unlock it if i remove it from my head to use some function on the screen..
Click to expand...
Click to collapse
Hi take55,
Yes, i'm aware of the advanced config tweak (also in HD Tweak), and as you correctly state, the screen should/will go blank on call connection (i'm running kwbr's A Touch Of HD 3.3.4 and mine doesn't, even with tweak applied!!).
Unfortunately, when the call ends and you move the phone away from your ear, the screen still stays blank????? I've read somewhere on these forums that it never will work like the iphone (not sure why, as the light sensor should recognise that we've moved the phone away from our ears).
So that is why i'm trying to get this other method to work. What i have noticed is that with the bmp copied over to the windows folder or with a cab i found by A-Math installed, my dialler locks up after every call (as if the transparent phone lock is in place) but i can't actually see it. None of the screen works and i have to soft reset. Maybe something is stopping the bmp to show on the phone....who knows.
It also might be the fact that this was designed for the Diamond (found the cab on the Diamond forums).
Just hoping some genius here might now how to sort this.
I've attached the cab file i've found, give it a try and see if you have the same issue as me.
Regards
DF
chanmama said:
hi, where you found out this software? it look's great, can you share the link to me? recall i saw some post like this, but just for diamond, i'm looking one for my hd, is there anyone have?
Click to expand...
Click to collapse
Hi chanmama,
Found the cab file for you, see previous post.
Regards
DF
Datafanatic said:
What i have noticed is that with the bmp copied over to the windows folder or with a cab i found by A-Math installed, my dialler locks up after every call (as if the transparent phone lock is in place) but i can't actually see it. None of the screen works and i have to soft reset. Maybe something is stopping the bmp to show on the phone....who knows.
Click to expand...
Click to collapse
It has nothing to do with the BMPs but with the registry setting that the CAB also makes. It sets HKLM\Software\HTC\Phone\PhoneLockEnable to 1, in wich case you'll have to press the power button to unock (no need to soft reset). For the BMP to work the phone/dialer software will have to support it, otherwise it just locks the phone in the usual way: black screen, power button to unlock.
Datafanatic said:
Hi chanmama,
Found the cab file for you, see previous post.
Regards
DF
Click to expand...
Click to collapse
tks but your cab only for the canvas skin only, do not contain the original software (slidable canvas), anyway, tks for your help
I've also found this problem to be quite annoying during a phone call but have found some sort of way to deal with it.
Firstly my ROM isn't tweaked, its just the basic one already installed.
After a call is connected, the screen switches off. But if you need to access the screen again during a call, I just press the "Back Arrow" key, one of the four hard buttons on the bottom which brings the screen back up again.
If you press the phone button instead whilst the screen is off, the screen lights up again but it puts the call on hold.
This probably isn't the best way to deal with this, but it seems to work for me for the time being, hope this helps anyone else here.
rubbermonkey123 said:
I've also found this problem to be quite annoying during a phone call but have found some sort of way to deal with it.
Firstly my ROM isn't tweaked, its just the basic one already installed.
After a call is connected, the screen switches off. But if you need to access the screen again during a call, I just press the "Back Arrow" key, one of the four hard buttons on the bottom which brings the screen back up again.
If you press the phone button instead whilst the screen is off, the screen lights up again but it puts the call on hold.
This probably isn't the best way to deal with this, but it seems to work for me for the time being, hope this helps anyone else here.
Click to expand...
Click to collapse
Useful info - I found this particularly annoying yesterday during a ouple of calls.
Also discovered Gyrator tries to turn the phone screen and was laggy - which was even more annoying!
Everyone!!!
CHECK THIS OUT - http://forum.xda-developers.com/showthread.php?t=489034
Answer to all our prayers - a screen lock which uses the g-sensor and not the light sensor.
Now, when a call is connected, holding the phone to the ear blacks the screen, but when you bring the phone down (to use the keypad or something), THE SCREEN COMES BACK ON!!!!!!!
Tried and tested on kwbr's A Touch Of HD v3.3.4 (probably the best manila2 ROM out there!)
Regards
DF
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.
all was well with my Dinc except for I had 2 blown speakers. I ordered new ones from ebay and replaced both. After replacing both, the bottom of my screen seems to not be working correctly. Whenever I go into SMS and hit the bottom for the keyboard to come up, it doesn't. I try using Whatsapp and it does the same thing. Its weird because the "attachment" button on the bottom of a sms works fine. It might just be that bottom/middle area. Is there any way to fix this? I had a feeling once I removed those ribbons to replace my ear speaker It was gonna mess something up .
I'm on MIUI android 2.3.5.
Is there any fix to this? or am I gonna have to just live with it for awhile?
EDIT: forgot to add, when I'm in WhatsAPP and I try clicking the bottom to bring out the keyboard, it highlights the message a little bit above where the text box is at, so its not reading where I'm pressing correctly. Its reading a little higher when I press in the bottom/middle area of the screen. Hope I explained that well enough for you guys to understand
A quick way to test if your screen is buggered is to downloading a drawing app and try to draw on the parts of the screen that you think aren't working. If you can't draw there you either a.) didn't connect a ribbon all the way b.) damaged a ribbon c.) electrically damaged something.
or d.) terrible coincidence and your touchscreen was on its way out anyways
It might be time for a new touchscreen. I had a similar problem where my screen wouldn't respond to touch in certain parts. I never took apart my phone prior to that so it wasn't (i don't think) my doing. Replaced with a new screen and I was good to go.
Take apart your phone and disconnect/reconnect the ribbons to ensure they are on there good. If that doesn't solve it I'd say a new touchscreen is in your future
Hey guys, I've got two problems with my unrooted stock HOX , which both are touchscreen related
1. When I push a little harder on the upper right corner of the touchscreen while in lockscreen, the diplay recognizes 3 other inputs on the left side of the screen (all of them about 2cm apart from one another, sometimes there are even more inputs randomly placed) which are slightly shaking but always appear in the same places. When this occurs, the display doesn't recognize any other inputs for about 4-5 seconds, then the 3 faulty inputs disappear and touchscreen works again. Okay, this could be of the harder pressure but the thing is, that when I'm doing the same in my homescreen or somewhere else, it doesn't happen. The problem with this occurrence is, that I often can't unlock my phone immediately and it also appears when I get an incoming call, so I am unable to answer it the green circle won't react on my input. But the fact, that it only occurs in lockscreen makes me wonder if it could be a simple software error and not hardware.
2. Sometimes (usually in combination with problem number 1) a part of the diplay doesn't react to any input whatsoever, but the rest of the screen does. I usually recognized that while typing messages and the area affected is an about 1cm high horizontal strip which is located in the height of the letter A in the portrait keyboard and goes all over to the letter L (I hope you understand what I mean ). I made it visible via a painting programm and it's a perfectly straight area. But when I now turn the display off and on, everything is fine again, so this makes me think (and hope) that this is a software error too.
I tried factory resetting but this wouldn't work out, at least the first problem still occurs (did the reset yesterday, so I can't rule out, that the second one still exists). I don't want to send my HOX in again, because this one is apart from that very nice and has no other faults.
So the main question is: soft or hardware and what could I do against this?
Hope you guys can help!
Hi,
The title speaks for itself.
Big issue here, long-press on the screen of my D855 doesn't work anymore.
Touchscreen is fine but long-presses just acts like a normal press.
I can't tell when exactly this bug started but it's really annoying since some actions can't be done without it (can't move icons, play specific games, etc...)
The lower end of the screen works fine tho (navigation buttons and apps dock) but everything above don't.
Some rare times it works with no particular reason.
Can someone help me with this ?
Is it hardware or software related ? (updating firmware to V21a didn't solved my issue).
Bu chance u aint got a glass protector on do you
No glass protector.
Stock Rom.
This is a really weird bug because it works 1 time after a "pinch to zoom" for exemple and then again it stops working
Off top of my head try if ure rooted xposed like g3tweakbox or gravity box one of 2 change long press behavior or or goto acseability and change touch feed back time to short
I have the same problem, whenever I scroll down/up, it goes directly at the bottom/top. Sometimes, it goes back to normal, I don't even know why but frequently it goes back to the problem. I had already gone to Accessibility, ..., set it to slow and it seems not to work. What to do? :/