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've been trying to pour through the API and find a way I can access and disable the proximity sensor with some code, but have been unsuccessful.
Does anyone know of a way, rooted or unrooted, that I can disable the proximity sensor completely?
I searched the forums and the only ways I found seem applicable to WinMo based phones.
Heck, I'll pay for a way to do it, I hate the proximity sensor that much.
Even if someone knows of a way I could disconnect it by opening my phone, I might even spring for that - but obviously a software approach would be much more appreciated...
Thanks!
redball said:
Heck, I'll pay for a way to do it, I hate the proximity sensor that much.
Click to expand...
Click to collapse
Why do you hate it, if I may ask?
larsrya8 said:
Why do you hate it, if I may ask?
Click to expand...
Click to collapse
It is unreliable, and I know it isn't just my phone because a number of people I know also have an HTC Incredible and it seems to behave just as erratically on theirs.
Based on the code I read through for Phone.apk or whatever, it seems like it is supposed to disable the proximity sensor when you're using bluetooth, just like when using the speakerphone - but it doesn't. I can't figure out why, and I noticed another thread floating around with users having the same issue.
I want to be able to use my phone while on a call and not have to worry about a shift in overhead light or something passing over the sensor and flipping the screen off while I'm trying to use it.
I would much prefer the ability to disable it entirely, and have full control of the screen off/on using the power button.
There was one app on the app store recommended in my searches that let's you lock the screen on and only go off based on orientation or something, but it doesn't seem to work for the HTC Incredible
Try screebl? Should keep your phone on based on orientation, I think even during a call? Not sure though.
Sent from my ADR6300 using XDA App
drawde said:
Try screebl? Should keep your phone on based on orientation, I think even during a call? Not sure though.
Click to expand...
Click to collapse
I tried Screebl, too...but unless I'm configuring it wrong - it doesn't seem to work while in phone calls.
I hate it too. Makes my screen turn on and off when I use my bluetooth.
Sent from my HTC Incredible
I'm right there with you on this. I really hate being on a call and having the screen turn off and have to shake the phone around to be able to end the call.
JTCGiants56 said:
I'm right there with you on this. I really hate being on a call and having the screen turn off and have to shake the phone around to be able to end the call.
Click to expand...
Click to collapse
That's the worst! It's like it gets doubly worse just when I want to be able to hang up.
If it helps anyone...I found these links. (If you google for "mProximityWakeLock", and follow the first Stack Overflow link, it also has two links in it to PhoneApp.java and InCallScreen.java)
I tried making an app that just kept calling release(), but it ended up just creating force closes.
you guys should email HTC so t hey fix it in the next OTA.
I know this is not really about droid, but what proximity sensor also does is scale down CPU speed (even despite using setcpu) making Skype completely useless without a headset.
When you initialize a call - everything is cool.
If you hold your phone on your hand and use loudspeeker - it's cool.
As soon as you put it to close to your face/ear - not cool anymore. To the point where it's absolutely impossible...
Cheers!
It does check for a headset plugged in, bluetooth audio or the speakerphone enabled. For bluetooth, it gets a code from a getState method. It only prevents the screen from turning off if it equals a specific state. All you have to do is force it to always be true.
You can also put this in the build.prop to completely disable it.
Code:
gsm.proximity.enable=false
How i do this?
ihtfp69 said:
It does check for a headset plugged in, bluetooth audio or the speakerphone enabled. For bluetooth, it gets a code from a getState method. It only prevents the screen from turning off if it equals a specific state. All you have to do is force it to always be true.
You can also put this in the build.prop to completely disable it.
Code:
gsm.proximity.enable=false
Click to expand...
Click to collapse
I m a nerd....how i do this ? where i write this code in my htc desire?
Thanks
1. you need to be rooted (if your on this forum and running miui you already are rooted) and have ES File Explorer downloaded from market.
2. open es file explorer and press menu then settings scroll all the way to the bottom and go to root options & turn on root explorer & mount file system
3. go back to the view of your sd card now on the top left there is a image of sd card click that. look for a folder named system and click there
4. in system scroll to bottom and look for a file called build.prop long press on this file and click copy now click the house at top left and paste the build.prop to your sd card
5. now go back to the system folder click on build.prop and you will get a selection of apps to pick from depending on what you have installed. pick es note editor
6. now that you in your build.prop scroll down and WHERE i put "gsm.proximity.enable=false" ? i write this code where? in the end? Where?
Thanks
I need Help please
i need help in
http://forum.xda-developers.com/showthread.php?p=15689458#post15689458
Quick fix
I had a similar problem with my phone (Samsung Galaxy S2) when I put it in a waterproof box. The display went black when someone was calling, and it didn't reappear unless I opened the box and thereby deactivated the proximity sensor reading.
My quick fix is to put a piece of black electrical insulating tape over the sensor. Since the sensor basically is a light sensitive receiver looking for tiny reflections from a coded light source, total blackness will be read as "no near object".
But of course, a nice API call would be more elegant
For the love of god, bump!
Bump....seriously.....I've been looking everywhere for a way to disable proximity sensor. I wish Tasker had a simple Disable/Enable toggle on this sensor
Follow the post at the top of this page.
Make a backup of your rom just in case.
In summary, if you have root explorer then here's how I'd do it.
1. Navigate to /system.
2. Click the button at the top that says Mount R/W.
3. Open the file called build.prop.
4. At the bottom of the file add a line that says:
gsm.proximity.enable=false.
5. Hit menu, save and exit, reboot
It should work. If it doesn't you still should be ok. If unsure go ahead and restore your backup.
have the same problem but with incredible s. the screen goes down until on other end some body will not put the phone down! iv trued the false method. it did nothing.
Disabling Proximity Sensor works!
ihtfp69 said:
It does check for a headset plugged in, bluetooth audio or the speakerphone enabled. For bluetooth, it gets a code from a getState method. It only prevents the screen from turning off if it equals a specific state. All you have to do is force it to always be true.
You can also put this in the build.prop to completely disable it.
Code:
gsm.proximity.enable=false
Click to expand...
Click to collapse
For all those who are looking for a solution to a faulty proximity sensor and nothing else works, I can tell you that modifying the build.prop as described does work!
I simply can now press the button to turn the screen on or off while on call instead of relying on faulty sensor. Very pleased.
This was done using HTC WILDFIRE S a510a running HTC Sense GingerBread 2.3.3 which has been rooted with CWM root through CWM custom recovery installed after unlocking the bootloader at the HTCDEV site. The program used was called Rom Toolbox Lite and I used the "build.prop Editor" feature to safely make the modification to the file.
Ok, I did a search several times and each time I came up with like 4,000 posts to read.
Is there a way to modify the apps shown on the buttons on that screen? I love that they are there, and I use 2 of the 3. I use phone and Mail, but I do not use the default Messenger, I use Hancent, and I dont use the camera from this screen and would like to replace that.
Thanks,
Doug
Yup. Go to personalize > lockscreen, and them choose which lockscreen. In there, there is a settings button for the apps
Sent from my PC36100 using XDA App
OMG! THANK YOU. I feel like a dumb piece of crap. It was staring me right in the face and I did not see it.
thanks again.
I dont have a thank you button showing anywhere on the forum.
Dammmmmiiitttt... That Makes 2 of us. thanks.
also if you use a launcher other than sense ie launcher pro or adw, you have to make sure you switch back to sense before you can change the icons.
I've searched. I thhought I had this set up before but it may have been on another rom. Is there a way to keep my phone to going to the lock screen when it is plugged in? Thanks in advance.
Also, any apps you want on the lockscreen need to be on internal memory, they blank out if they're on sd.
Rather then start a new thread, I will ask my issue here since it is for Synergy, and a lock screen issue. Is there a way to lock the screen while on a phone call? I use a BT headset, usually answer the call from the headset and leave my phone in pocket. Problem in the phone unlocks when the BT headset answers the call, and funny things can happen to the phone while sliding around in my pocket while I work. Not to mention the battery life is decreased since the screen is on.
A related question, on Froyo somehow I could have the phone set to answer to the headset if I used the headset to take the call, or if I answered from the phone it would switch to the phone for speaker/mic. Any suggestions how to set that on this ROM?
Thanks in advance for any suggestions!
I'm not sure when it stopped but I don't have a lock sound. All other sounds are working, like the unlock sound.
My GSM GNex is on 4.0.3 and AOKP b27. I have Screen lock sounds checked in Settings > Sound
How can I fix this?
3bs11 said:
I'm not sure when it stopped but I don't have an unlock sound. All other sounds are working, like the unlock sound.
Click to expand...
Click to collapse
??
So your unlock sound is or isn't working?
Do you have a file named lock.ogg and unlock.ogg in /system/media/audio/ui?
RMarkwald said:
??
So your unlock sound is or isn't working?
Do you have a file named lock.ogg and unlock.ogg in /system/media/audio/ui?
Click to expand...
Click to collapse
Sorry about that. I meant my LOCK sound isn't working
Yes I just checked using root explorer and I have both those files.
3bs11 said:
Sorry about that. I meant my LOCK sound isn't working
Yes I just checked using root explorer and I have both those files.
Click to expand...
Click to collapse
Maybe try pulling the lock.ogg file from another ROM, replace it in that folder, and see if that works...?
RMarkwald said:
Maybe try pulling the lock.ogg file from another ROM, replace it in that folder, and see if that works...?
Click to expand...
Click to collapse
I tried replacing it using root explorer but it said I can't because it's read only. I don't have access to the files when I use my Mac, I can only see what's on the internal sd card.
3bs11 said:
I tried replacing it using root explorer but it said I can't because it's read only. I don't have access to the files when I use my Mac, I can only see what's on the internal sd card.
Click to expand...
Click to collapse
i don't know why google doesn't have system volume under sound settings
anyways OP download an app
search audio manager on the market (google play now)
hide it pro will come up, its actually an app that hides pics n stuff but also manages sound
once you download it open it
you will see system volume, you have to turn this one up for the lock sounds
also if your phone is on vibrate / silent, lock sound will not work (which makes sense cuz you don't want any sound out of it)
also make sure your lock screen sound is on in settings - sound
and there you have it
you can hear it lock and unlock
3bs11 said:
I tried replacing it using root explorer but it said I can't because it's read only. I don't have access to the files when I use my Mac, I can only see what's on the internal sd card.
Click to expand...
Click to collapse
Click the "Mount R/W" button in Root Explorer
beans_p_ said:
Click the "Mount R/W" button in Root Explorer
Click to expand...
Click to collapse
I replaced it but it still isn't making a sound.
subxero123 said:
i don't know why google doesn't have system volume under sound settings
anyways OP download an app
search audio manager on the market (google play now)
hide it pro will come up, its actually an app that hides pics n stuff but also manages sound
once you download it open it
you will see system volume, you have to turn this one up for the lock sounds
also if your phone is on vibrate / silent, lock sound will not work (which makes sense cuz you don't want any sound out of it)
also make sure your lock screen sound is on in settings - sound
and there you have it
you can hear it lock and unlock
Click to expand...
Click to collapse
I'll try that out thanks
i think i figured it out
i was having the same problem you were having and found your post. you are no longer getting the "locking" sound when you hit the "power" button on your phone, but all other sounds are working, right? i think i figured out the solution/issue. let me know if this works for you:
it is because you have a "lock delay" on your phone via the settings/ROM control, and as such, the phone is not locking when the screen shuts off. hence, no lock sound when you hit the power, but everything else is working.
make the following changes and let me know if it fixes your problem. . . it fixed it for me at least:
1) go to "lock screen options" in the ROM control settings menu and uncheck "wait to lock screen."
and/or
2) go to "security" under the regular settings and "automatically lock" to immediate.
now when you lock your phone it will make the lock sound. if you are testing it by serially locking your phone, make sure you drag the circle over to unlock it before locking it. if you wake the screen and then press the power button it won't make the sound since i guess google is being very technical regarding what exactly qualifies for a lock.
this is my first post - not sure if i broke any rules, but i hope this helps you and anybody else with a galaxy nexus who became convinced that were was an AOKP software bug, but in actuality, it is normal function of the phone.
maguro (usa version) - aokp milestone 5.
Thank you avinashl :good:
PLEASE help me i spent 6 hours trying to figure this out last night. I'm trying to figure out which .kl file in /system/usr/keylayout control's media keys (play/pause) (next) (previous) so i can remove the wake function from them and make my screen stay off when i use a bluetooth headset.
ANY HELP WOULD BE AWESOME
what i know... the device output from keytest when pushing the buttons.
the button numbers are 163, 165 for next and previous and 200 and 201 for play/pause (keycodes)
deviceid=15
source =0x101
action =ACTION_DOWN
keycode=MEDIA_PLAY_PAUSE (and next previous etc)
scancode = 201 (for play pause #2)
you can substitute in but the main problem is i can't identify the file that controls these fuctions.
the guide to keylayout files is here: http://source.android.com/tech/input/key-layout-files.html
i tried some fuctions i found in google searches and i was only able to get a list of 13-14 deviceid's and 15 is always missing so i can't figure out how to identify it.
plz help ty.
most devices use a file h2w_headset.kl or sec_key.kl but neither has desired effect on p935 (telus p930)
i also have checked stock roms for telus, atnt and bell and they have differant keypad files for each.
i_atnt-keypad
i_bell-keypad
j_jts-keypad (telus)
i am running a atnt rom, i tried editing the atnt file, that didn't work, so i added the telus file too, that didn't work. is this possible to fix or do i have to get a stock telus rom to fix it?
my phone is p935 telus but some of the internals say p930
OK so the ONLY way i can find without having a developer write a flashable zip that modifies policies etc to disable the media keys from waking up the device on a car bluetooth stereo (because it kills the battery hard if every time you skip a track (which you do from car controls while phone is in pocket) the screen comes on for 30 seconds) so the only way to avoid it is quite simple, make either a pattern, face, or password lock. for some reason the dev's think that swipe unlock and no patter or swipe means you want your screen to turn on every time you change a song from a headset control, it makes 0 sense but whatever, atleast i found a workaround, i don't mind pattern unlock it takes 1/3 of a second if its a simple pattern, and it prevents my screen from coming on 10-15 times a day for no reason except to waste battery etc.
This is partially solved unless someone comes up with a way to disable media keys without having to have a lockscreen that has a password (private message me plz i'll be very happy)