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 noticed after upgrading to Lollipop that it was difficult to navigate menus near the top of the screen in some apps. I turned on the "pointer location" option and sure enough I found very strange results.
i.imgur com/tPdVowo.png (you'll have to add a period after the domain name, new user status prevents me from posting links)
This first screenshot is me running two fingers all the way to the top of the screen, and once i reached the top i ran them towards the edge of the screen. As you can see there is an area where the pointer location bugs out.
i.imgur com/bh5hWeV.png
This image is just a single finger running horizontally across the top of the screen. The top line is where my finger actually was, but the phone also registered extra touches as you can see from the line below. There's even a section where the top line didn't register at all.
This is a Verizon phone, never been rooted, and hasn't been dropped or wet. I noticed while making this post that the area i am having issues with aligns almost perfectly with the top part of Sense's notification menu.
Is this normal or do I need to exchange my phone?
I am having the same issue with my phone. When I turn on show touches in developer options or install a multitouch test app, it'll show an extra touch just below where I'm touching but only when I'm touching at the top of the screen. Stock lollipop, never rooted, no water damage.
Bump
same problem. do you have s-off? downgrade firmware and rom - maybe this fix problem?
bumbarush said:
same problem. do you have s-off? downgrade firmware and rom - maybe this fix problem?
Click to expand...
Click to collapse
I don't. I didn't want to do that yet. Was hoping to see if anyone else had the issue and if they were able to resolve it.
Just want to see if anyone was able to resolve this issue.
fixed!
we need the old piezo lighter's element. The phone must be turned off. A few strokes on the screen near the problem area, and voila, the screen works again. Do not be afraid, the phone will not be damaged
i
on russian:
http://4pda.ru/forum/index.php?showtopic=496511
First things first: This is a crosspost from https://forums.lenovo.com/t5/Moto-Z-Play/Bottom-part-of-screen-non-responsive/td-p/3630276. Hope this is ok.
Hello,
I have a problem with the touch screen. I noticed that pressing the home button isn't recognized every time. Sometimes nothing happens (no vibration, nothing).
So I investigated a little: I turned on the developer settings, enabled the "Pointer location" option so that the OS shows the path where I drag my finger.
I then dragged my finger from the bottom left/right of the screen into the bottom center in different arches. You can see the result in the attached file on the left side. (I combined all screenshots into one image)
What I came to find is that apparently there's a dead zone in the middle of the bottom of the screen!!! I have marked this area approximately with a red ellipse on the right side of the attached screenshot.
What can I do to remedy this issue? Do I have to RMA my phone? Can I solve this with a screen recalibration myself?
Please advise,
Best regards,
Chris
Attachment: http://i.imgur.com/v4QfDyB.png
EDIT:
Found the culprit! "Fingerprint Quick Action" (com.ztc1997.fingerprint2sleep) was responsible for this behaviour! That's sad, because I liked the additional home button via fingerprint reader...
I also use the app and experience the symptom. Thanks for the info, good to know at least what is causing the problem...
Hello,
I have a rooted ( Magisk-v14.5 ) OnePlus 5t with Android 7.1.1.
Without me ( knowingly ) changing any settings suddenly the following behaviour occurs:
While I am typing in an App like Tinder, E-Mail etc... the virtual keyboard keeps sliding down like i touch the little triangle button on the left bottom corner. But of course I am not accidentally touching it.
Sometimes the Keyboard is sliding down without me even touching the phone.
This behavior seems rather random, sometimes it works for hours ... sometimes I can hardly type anything.
For me it looks like some "App / Process / Command " is trying to take over the input controls of the phone but it never shows up
I use the most updated version of "Gboard"
I tried the following:
1. de-install "Gboard" and use other keyboards like "SwiftKey Keyboard"
2. changing all settings the I somehow would relate to keyboard inputs
3. I used the " developer options -> input -> Show taps / Pointer Location " to check if maybe my touchscreen sensors are broken and the phone actually registers an touch at the point where the little triangle button on the left bottom corner of the keyboard is. => No touch registered
Can someone help me or has similar experiences and a solution ?
So i bought a oneplus 5t with a slightly cracked (only one crack on the top of the screen, and it's not catastrophic) but (almost) fully functional screen.
It detects every touch accurately, 3 fingers same time, etc.
The only problem is, when i want to swipe (even on the home page, when u wanna scroll down the status bar f.e.), it stops scrolling the exact moment i take off my finger, or scrolls just a little bit.
I'm aware, that the crack on the screen might be causing it.
I did the factory mode calibration. I did reset the whole phone, hoping the problem somehow gets solved, but it didnt change anything.
The problem is very consistent, therefore it's useable, if you accept the fact, that the screen responds only when your finger is touching it and no longer.
I feel like if i could change the sensitivity of the touchscreen, or the responsiveness on the gestures it receives, i were able to make it just as new.
Oneplus 5t (OOS 10.0.1, TWRP and Magisk installed, in case you have some app or sth that requires root)
(I couldnt find the parameters that has relation to touch sensitivity in the build.prop file, i'd be glad if someone linked me a guide)