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 have ATT Fuze. I downloaded the 20100503 package, extracted it. Put STARTUP.TXT from Fuze folder. Updated zImage and rootfs.img and modules, and it boots fine.
However, when I press 'Home' key, I get a slider sometimes, sometimes it takes me to random weird screens, and sometimes it does nothing. Other keys do not seem to work as expected either, but I haven't documented them.
Another issue is that when I make a call, the screen goes black. The call works, but then I can't seem to get it out of the black screen without removing the battery.
Any help appreciated.
esac17 said:
Another issue is that when I make a call, the screen goes black. The call works, but then I can't seem to get it out of the black screen without removing the battery.
Click to expand...
Click to collapse
I have a RAPH120, and this is one of the more annoying bugs for me.
One way to try and get the screen back is to open the slide-out keyboard.
i have the same issue i serched and serched and couldnt find anything so i thought it was just me they keybord trick dosnt work for me tho
keyboard trick doesnt work for me either. ive pretty much given up on android for now, its nice but not usable .. (although i admit, a little better than winmo which is not nice and not usable)
personaly i think that the camera dosnt need attention id be fine with out it hopefully they will work on this tho
Hi,
I have a Tilt 2 with stock ROM. The only two enhancements I use is "S2U2" and "Advanced Configuration Tool" ! I changed someting and now have a little problem :
When I get an incoming call and the caller id with the pic pops up, I can't pickup the call, using the green on-sceen button. This button does NOT pickup the phone call. I have to use the green hardware button to pickup the incoming call. However, I can use the RED on-screen button to end the call.
I soft reset the phone a few times and tried some settings with the "S2U2 and Advanced Config. Tool", but I can't get it to work.
Any ideas ?
I'd appreciate any help and suggestions.
Thanks,
JCE
same thing is happening to me, neither the onscreen slide, or the hard button work..
can't wait for an answer -_-
i lurk this forum here and there, and i still don't understand anything...at all -_-
jerzey_devil said:
same thing is happening to me, neither the onscreen slide, or the hard button work..
can't wait for an answer -_-
i lurk this forum here and there, and i still don't understand anything...at all -_-
Click to expand...
Click to collapse
Haha, it takes time to understand all the jargon and such that takes place around here. Just do some reading and searching, don't be afraid to ask questions if you can't find a thread explaining it. Eventually I would suggest flashing to a good rom like one of the Energy Rom's or a Cell Rom. The two best Rom Cooks on the Rhodium (Touch Pro 2/Tilt 2) side of xda.
I say the same thing as doublen1, use a non-stock ROM because these come with features already installed and you will be able to use S2U2 and all that stuff. and about the actual issue, I have had problems picking up calls with the screen, so I just started using the hardware keys.
Make sure you didn't mess around with any of the touch screen settings in Adv. Configr or BSB tweaks or something like that. This usually causes the problem with the dialer.
Hi AllTheWay,
well, I don't remember changing anything in the "Advanced Config. Tools" which would cause the touch screen settings to be different. However, I might have done or changed something...... Is there a way to get the "Touch Screen" settings to a default level without hard resetting the device ?
Thank you.
JCE
jce2005 said:
Hi AllTheWay,
well, I don't remember changing anything in the "Advanced Config. Tools" which would cause the touch screen settings to be different. However, I might have done or changed something...... Is there a way to get the "Touch Screen" settings to a default level without hard resetting the device ?
Thank you.
JCE
Click to expand...
Click to collapse
Not that I know of off the top of my head. There might be a setting inside of Adv Config that would allow you to restore to default. Also the S2U2 has a setting to take control as the dialer screen when somebody calls. You can try messing around with the settings in S2U2 as well.
PM me if you don't find an answer soon.
Standard (edit: standard HTC desire) Froyo, answered a call while browsing the market, and suddenly had a very strange call screen.
It had 4 buttons (add call, pause call, in addition to normal mute and speaker) instead of the normal 2, and the lower bar a smaller end call button plus some extra ones!
Its back to normal after a restart...
Whats going on?
http://static.googleusercontent.com...gle.com/en//googlephone/AndroidUsersGuide.pdf
Thank you!
But those are not the sense screens (they are standard android) and not what I saw. Appreciate your help, must be difficult to imagine what I am trying to say just from a description. WIsh i had taken a foto....
PS have edited my original post to reflect its HTC froyo; my mistake!
was it like in this thread but obviously not skewed to one side
no link in your message....
lol http://forum.xda-developers.com/showthread.php?p=7600397#post7600397
doh
THATS THE ONE!
But mine had the contact card, and the "numbers" button on the bottom row (Since i was on a call) and a little end call button!
so strange......
BUT thanks for solving the mystery somewhat, at least I know im not going mad!
I dont get them buttons on mine but can get buttons that do the same thing by pressing menu during the call. Maybe there is some sort of shortcut to enable them? I would be interested to know if there is as well.
Its probably a hidden screen in the system that was never used, but somehow gets called up.
THis is how it happened to me, so try it, maybe its a reproducible bug. Browse the market, and get someone to call you, then answer....
Thid weird issue started today in the morning, first I noticed that the clock widget had changed size, and that the led me know ring around the cam hole was out of place, but, when trying to write in whatsapp, I no longer could make the keyboard to appear by taping the wrinting field, in fact, nothing located in the bottom worked, what is odd, the bottom gestures worked, as I hid the nav bar since day one, tried everything, changed dpi, changed keyboards, retired the screen protector, wiped cache, to no avail, reluctantly, I updated to android 10, but no luck, after digging more, I found a work around, I changed the resolution from quad hd to full hd, now all is normal, but, this is just a work around, not a real solution, somebody have an idea of what would be the reason for this?
Did you have your phone linked to windows, your computer online and the phone screen displayed at that time? In this case, if you chose to use your computer's hardware keyboard in Your phone settings on your computer, then, when trying to write something in whatsapp, the virtual keyboard on your phone is not displayed or it is partially displayed. In my case, using the AI Type keyboard, only the top row of the keyboard was displayed because the app thought I'm using my computer's keyboard.
Sent from my SM-N975F using Tapatalk
Thanks for your reply, but no, in fact I have never used the phone in that way, something else caused the issue
winol said:
Thanks for your reply, but no, in fact I have never used the phone in that way, something else caused the issue
Click to expand...
Click to collapse
Was your phone charging at the time by any chance?
I found the solution!
I had the exact same problem with my note 10 plus, the gestures worked, and I tested the bottom part of the screen to make sure everything was working and it was, but the buttons in apps like instagram at the very bottom of the screen still were unresponsive most of the time. The solution is to ho to your settings, switch the navigation bar to the other gesture variant and then back to you preffered one and it should work. It worked for me.
Thanks man, I just found what triggers the issue, as odd as it seems, changing resolutions from qhd to fhd id what causes the issue, odd, because I used a bixby routine to save power at nights, by setting medium power saving, which among other things, lowered the screen resolution to fhd, when the routine ended, it should reverse to qhd, and that precisely triggered the issue, I used this routine for months, until, out of the blue, it started to cause this problem