Database Users

[APP] hTorch v3.2 | using camera LED as flashlight [updated: 2008-11-20]

hTorch is a small application with a graphical user interface that enables you to use your Xperia X1 as flashlight.
hTorch is built for the HTC Raphael (aka HTC Touch Pro) and has only been tested on this device. Although users reported that it works on Sony Ericsson Xperia X1 as well. PLEASE NOTE: Use this application at your own risk! I’ve done as much testing as possible, and will try to fix every bug which will be reported but it's my first Windows Mobile application and I can not guarantee that it is free of bugs. NetRipper deserves most of the credit because my application uses his TorchButtonLibrary v1.0 to control the LED itself.
Usage:
The program installs itself into "%ProgramFiles%\hTorch" and also creates a shortcut into %StartMenu%\Programs\Accessories. The further usage is as simple as possible. Start hTorch using the shortcut. On program start the LED will automatically be turned on and you will see the programs main screen.
On the main screen you can:
enable and disable the standard LED mode using the upper left bulb button.
enable and disable the bright LED mode using the upper right bulb button.
disable the display using the lower left button (The display can be turned on again using the power button)
exit the application using the lower right button.
enable and disable the standard LED mode using the D-Pad Action hardware button.
enable and disable the bright LED mode using the D-Pad UP hardware button.
disable the display using the D-Pad DOWN hardware button.
PLEASE NOTE: The flashlight will stay on forever - there is no timeout programmed. So the only timeout is the capacity of your battery. Burning the LED should not be very likely as this posting explains but please take care anyway. Please also note that the LED can not be left turned on while the device is in standby. So if you want to use the torch for an extended period please use the display off button but be aware that the hardware buttons will still function!​pRequirements:
This program requires .NET Compact Framework 3.5 to run. If you are not sure if you have the Framework installed or which version you have installed please follow this instructions (.NET Configuration Tool)
Since hTorch v3.0 it is no longer necessary to uninstall TorchButton. They can now be installed both at the same time.
Version History:v3.2:
Added AppToDate support.
Some minor code optimizations.
v3.1:
Fixed several minor bugs
Fixed one huge bug preventing the device from standby even after hTorch was already closed.
Added a special error handling in case a user terminated hTorch instead of using the quit-button.
v3.0 (unreleased private beta):
Source again completely rewritten. I'm now using the TorchButtonLib v1.0 to control the LED. Which now also means that hTorch and TorchButton can be installed at the same time.
Action button mapped with LED on/off function.
"UP"-button mapped with LED bright on/off function.
"DOWN"-button mapped with build-in display off function (display can be turned on using the power button).
Changed right softkey to menu with sub menu items: "Quit", "Bright LED On/Off", "Display Off", "About".
Changed normal LED on/off button. (Artwork was done by obsidian73 - Thank You!)
Added bright LED on/off button. (Artwork was done by obsidian73 - Thank You!)
Added display off button. (Artwork was done by obsidian73 - Thank You!)
Changed the program window not to maximize (so that now the status bar is visible).
Added function to prevent ideling into standby (AndyZap - Once again thank you for your help!)
v2.2:
Updated TorchButton to v1.2 which enlarged the maximum timeout from 300 seconds to 86400 seconds (a day) - Thank you NetRipper!
v2.1:
Completely replaced all graphics to give the program a much more professional look and feel. (Artwork was done by obsidian73 - Thank You!)
Replaced the exe-file icon with a more diamond-like one
v2.0 (unreleased private beta):
Completely rewritten source so that hTorch can now detect the LED state
Tightened the program as much as possible (exe-file lost about a bit more than 25% of its size)
Automatically turn off the LED on program exit
Changed auto-off timer to 5 minutes (hard coded)
Added SoftKey functions
Added About Dialog
v1.1:
Fixed Bug when installing to Storage Card
Start LED on program start
v1.0b:
Initial version
On the picture you can see the programs
main screen with usage information:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Downloads so far (counting since v3.2):
AppToDate Users:
Do you like my work? Please consider donating:
Thank you for your support!​

X1 no longer supported
Due to the ongoing reports of damaged LEDs I now officially remove the X1 from the supported devices list!
If you still want to use hTorch you can find it in the raphael software forum but be warned: Sony Ericsson has not heat sinked the LED at all. It has been reported that using the bright led mode for just about 30 seconds already damaged a LED. Other users even reported problems after "just" using the standard LED (which is the same as in the camera software). I can not verify all this isues but I don't want to be sued for any damaged device. So if you are using hTorch on the X1, than you are doing it on your own risk!
:-(
A very disappointed
DeepThought
Do you like my work? Please consider donating:
Thank you for your support!​

Once more:
Due to the ongoing reports of damaged LEDs I now officially remove the X1 from the supported devices list!
If you still want to use hTorch you can find it in the raphael software forum but be warned: Sony Ericsson has not heat sinked the LED at all. It has been reported that using the bright led mode for just about 30 seconds already damaged a LED. Other users even reported problems after "just" using the standard LED (which is the same as in the camera software). I can not verify all this isues but I don't want to be sued for any damaged device. So if you are using hTorch on the X1, than you are doing it on your own risk!
:-(
A very disappointed
DeepThought
Do you like my work? Please consider donating:
Thank you for your support!​

nice app, however is it possible to automatically use the brighter led light from the start of the app?
thank you.

nap007 said:
nice app, however is it possible to automatically use the brighter led light from the start of the app?
thank you.
Click to expand...
Click to collapse
Thanks!
Unfortunately that's not possible at the moment but it's a planned feature for the next version of hTorch.
In the original thread I have provided a todo list of features which will be added in future versions. It can be found HERE.

Feature request
Maybe this is is already possible, but if not - please include the option to add a 'today panel' button. I'd like to be able to launch this app with as few steps as possible!

Very nice app - works perfectly on the Xperia.

Works great on the X1. Thanks for the app.

PLEASE READ! POSSIBLE LED DAMAGE on X1 in Bright mode!
Please read this carefully!
My friend was using hTorch on his X1. He had it on Bright mode for 1 minute... and then noticed the light was getting dimmer.
When he switched back to Normal mode, the flash LED became so dim it was barely visible, and the area around the LED was very hot. What has happened now is:
- The flash LED is still very dim, even after the phone has been off for a few hours, meaning that the LED is possibly damaged.
- The LED has moved from its original position in the centre of the round lens, and the light beam is no longer a perfectly round circle. Probably, some glue that is holding the LED in position has melted from the heat.
In other words:
HTC/Sony Ericsson has probably not designed the X1's flash LED to be used for long periods of time at its full brightness, i.e. as a torch. The LED in the X1 is probably designed without a proper heatsink, and will be damaged if it overheats.
Obviously I can't ask anyone to risk their X1 to verify what has happened to my friend, but I would suggest that X1 users not use hTorch in Bright mode at all, or at most for only about a few seconds. Maybe the developer could incorporate a safety timer in Bright mode?
And before the flames start, PLEASE DON'T GET ME WRONG: This is a true story and it is NOT a complaint against hTorch or its developer. This is simply a warning, based on personal experience, to fellow X1 users to be careful when using this application.

I am very sorry to hear that yodafone and I really take your post very serious!
But since hTorch is now available for quite some time and also had many X1 users before my posting in this forum and no such outage yet I think it was probably a faulty LED in first place.
Unfortunately I don't own a X1 otherwise I would take the risk of testing the bright LED for a couple of minutes. But I own a Touch Pro and I use the bright LED every night for about 5 minutes. The longest period I've used it was about 10 minutes but than I switched it off because the device was getting very hot.
I would try to RMA the device if I where you. Maybe the LED was not probably heatsinked in your friends phone because of some production fault?

There are two very valuable posts in the TorchButton Thread which address the risk of using the LED:
johnny13oi said:
I just wanted to comment on this. I am also a candlepowerforum member and know about the uses of LED's. I think that there is still the possibility of burning out these LED's inside the phones if they are high powered LED's which i believe they are. LED's have a very long life expectancy if they are properly driven and have proper heatsinking if they produce large amounts of heat. Given the light output of these phone LED's and being used as camera flash's I would assume that they are sufficiently high powered LED's drawing much more than the typical 25mA of 5mm LED's. And combining that with the probably nonexistant heatsinking of the LED's due to size constraints of the phone, I would believe that these LED's would definitely die or degrade dramatically if they were left on in high powered mode. If these LED's draw anywhere near 1W (~350ma at 3.7V) in high power, I wouldn't leave it on for too long.
Click to expand...
Click to collapse
johnny13oi said:
With the LED running at a constant 100-150mA, I would think that this would be fine for short periods of time. I would not however let it run for over 5 minutes. Heat buildup can happen very very quick and with almost no heatsink for the LED's, it would build up even quicker. LED's typically change color output when it is overheating or overdriven. Usually overdriven or overheating white LED's appear really bluish when this is happening. So if you notice a change in color output, I would definitely turn it off and let it cool.
Click to expand...
Click to collapse

thanks mate, but it wont work on mine - gives me some message about .NET framework?

Cant you already turn the torch on from the camera app?

i can do that no probs

big pimp said:
thanks mate, but it wont work on mine - gives me some message about .NET framework?
Click to expand...
Click to collapse
Have you even read the first post in this thread?

big pimp said:
thanks mate, but it wont work on mine - gives me some message about .NET framework?
Click to expand...
Click to collapse
Have you installed the .NET Framework? hTorch requires .NET 3.5 to be installed.
dadeadman said:
Cant you already turn the torch on from the camera app?
Click to expand...
Click to collapse
Of course you can. But it's not very handy is it?

Bright LED mode could cause damage?
Just to bring this to everyones attention: I just added this warning to the second posting:
Because of the possible damage of a X1 caused by hTorch as posted here: http://forum.xda-developers.com/showthread.php?t=456477&page=3
I did extended tests with the bright LED mode on my Touch Pro and can confirm that there was no problem even after 15 minutes of usage. But since I don't own a X1 I can not rule out that the LED in the X1 is not as good or is not as good heatsinked as the one in TP. As long as this is not clear, please be careful!

hi man..guess what ..yesterday only i was thinking of how i missed the torch feature of my W800i ..
btw my W800i also had a feature to blink the LED for 'SOS' in morse codes
can u program a button to transmit 'SOS' in morse codes?
u know..it blinks in morse code?

wha...? I never knew W series can do that? in fact, I'm surprised any phone could 'transmit' SOS signal using LED that been intended as camera flash.

Nocturnal310 said:
can u program a button to transmit 'SOS' in morse codes?
Click to expand...
Click to collapse
It's already on the todo-list for the next version. Unfortunately I'm quite busy at the moment so I can't promise when I'm able to release it. But at the beginning of January at the latest.

Samsung Galaxy S 3 Sensors!?

Hello,
So today i noticed on the left side of the speaker, that there are 3 sensors, both of them are together on the same place, which should be Light sensor and proximity sensor... but what about the other one more to the left? Seems pretty much like a Small LED to me.
Check this picture guys and u will see it clear enough!
http://www.sync-blog.com/wp-content/uploads/2010/06/Samsung-Galaxy-S-Series-Smartphone.jpg
Update after a test [Post #4]
Center: Proximity
Right: Light
Left: ?

Is one the light sensor for the auto-brightness thing, and the other two possibly a 'sender/reciever' set up for detecting when it's close to your face in order to turn the screen off during a call?

petethesparky said:
Is one the light sensor for the auto-brightness thing, and the other two possibly a 'sender/reciever' set up for detecting when it's close to your face in order to turn the screen off during a call?
Click to expand...
Click to collapse
I believe the proximity sensor and light sensor are both together, which leaves the left sensor... i wonder what it is
May be u r right, i am dying to find out!
I will test it with a Q-tip. I pointed a flashlight with high brigthness on the sensors now, the left one doesnt seem like a LED... so that option just kinda died

Ok tested it, qtip during the call shows that the proximity sensor is the one in the CENTER.
Used a black fabric for the light sensor... with my finger over the fabric covered the left and right sensors, result: RIGHT sensor is the light sensor!
Leaves: Left sensor.... what is it?
Center: Proximity
Right: Light
Left: ?

spy cam - big brother is watching you!
beats me i hadnt even noticed it!

I would probably guess that the two closest together are a Transmitter/ Receiver pair.
It could be emitting infra-red and using a receiver to detect how far away an object is based upon the light returned.
One way to sometimes 'see' this is to use a normal camera to look at it, if it shows a white spot, there is a good chance it's emitting IR.
Logicalstep

[SOLVED] Faulty proximity sensor - hardware fix

Caution: not-so-skilled people ask for help to more skilled friends !!!
How a proximity sensor works:
Basically there is a modulated infrared emitter and a correspondent IR receiver. When the modulated light is reaching the receiver, the sensor will become active.
In the mobile phones, the structure is built like in the below drawing. When an object is close enough, the reflected modulated light will be captured by the sensor and it will activate it.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
The problem in some phones is that for various reasons the sensor is hyper-sensitive. This should be translated to sensor becoming active when an outside object is even fairly far from the glass surface. But the problem is exactly the glass surface. The sensor is so sensitive it will catch even the refracted light from the glass (remember optics studied in school ?). Some of the light emitted by the emitter will be refracted from the very glass body back to the receiver.
The temporary fix was to "rub" the sensor area while in a call and suddenly the sensor was acting normally. This was caused by the fact that all that reflected light (from the finger) was supersaturating the sensor so, when obstacle was removed, the sensor was no longer hyper-sensitive, at least until the next power-up (next call).
The solution I tested (and apparently it works) is to create some sort of a light attenuator to place in front of the proximity sensor, but under the glass. Well .. the idea came to me while fixing an old remote control .
I'll let the pictures below to speak (thousand words for each ... pretty long story ) ... click on thumbnails for full 1200x800 size.
In case you are applying the mod, please leave a word here, so me (and others) will know the outcome.
I had not even a proximity misfire since I implemented this (roughly 48 ours ago) .
The opened phone (you will fond on the web lots of HOW-TO's about dismantling the defy):
The front case and the board - parts of interest:
Close-up:
Filler material :
"Attenuator" mounted:
View with the phone assembled back:

This seems really promising, I'll give it a try when I can find a suitable translucent material and post the results.
Sent from my MB526 using xda app-developers app

Very cool!
The proximity sensor is actually a part of the motherboard, interesting.
So in my case that my proximity sensor is broken and my LED is permanently on, the only way to fix it would be getting a new motheborad, in another words a new phone. Right?

Google Cardboard

Anyone used their Z2 with google cardboard before?
Does it fit and do the magnets work?

Im just waiting to receive the carboard pack from Amazon
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Tomorrow night i Will tell you how the Phone fits and works

dnydny said:
Anyone used their Z2 with google cardboard before?
Does it fit and do the magnets work?
Click to expand...
Click to collapse
I use my Z2 with Google Cardbaord and it works. Unfortunately, the magnet screen tap doesn't work.
As an alternative I glued a piece of aluminium foil to the side of the cardboard so the inside end touches the screen. You can then tap the screen by tapping the aluminium foil. It can be a bit hit-and-miss at times but its better than nothing. I use a PS3 controller, too.

Magnet button can be made to work
I've noticed that the magnet sensor in the Z2 is located on the lower part of the phone which unfortunately ends up too far away from the magnet button. Putting the phone up-side-down makes the button work but the view does not rotate right. I'll try moving the buttonto the right side of the Cardboard.
/ KJ

It Works
G'day Fellas,
Google cardboard works just fine with the z2, the only issue as mentioned is that the magnet doesn't appear to work. I can confirm that if you relocate the magnet from the left hand side of the cardboard to the right hand side it does indeed work with the z2.
You will need:
A knife, or strong fingernails to remove the glued on magnet
And some superglue or epox mix.
Simply move both magnets from the left hand side to the right and voila it works. You can even cut a channel into the right hand side for the second magnet to slide in if need be, so far it works just fine without having to do that. :laugh:

dnydny said:
Anyone used their Z2 with google cardboard before?
Does it fit and do the magnets work?
Click to expand...
Click to collapse
I have just got myself the Xperia Z2 (originally had a Note 3 but needed a smaller screen phone) and tonight although I don't have a Google cardboard I have got instead the more user friendly ColorCross HMD and found that with my Z2 the magnet works directly where the magnetic charger socket is. Also from my own experience the Z2 works as a better screen then the Note 3 due to a higher pixel per inch resolution and 5grams lighter

It works.
It does work on the Xperia Z2, and as some people have said, for the magnet button to work you have to move it to the other side of the box.

guille00 said:
It does work on the Xperia Z2, and as some people have said, for the magnet button to work you have to move it to the other side of the box.
Click to expand...
Click to collapse
If you notice from my posting I have got a Z2 and the magnet has to be moved from the top of the phone to side with the magnetic charging socket as the magnetic sensor is also in that location

I've been using my Z2 with the I Am Cardboard 45mm kit and it works well once the magnet is moved. The screen is a bit too large so apps aren't always correctly in the field of view. I've added padding and a headband to mine to make it a little easier to use. Has anyone had success with one of the kits for "large" phones? I can't adjust focal length with mine so moving the screen further away from the lenses won't work. Different lenses might do the trick but some kits come with adjustable lenses.

Does anyone faced heated z2 whilst using cardboard....m using Vr Cinema for movies....any solution for it??

Google cardboard unstable
I've recently bought a google cardboard. When I watch videos using the cardboard, with VRse or the NYTimes VR app, the video flicks or jumps every other second. It's as though it was not stable. If I don't use the cardboard, watch them in one full screen it all goes fine.
Any idea?

pablarribas said:
I've recently bought a google cardboard. When I watch videos using the cardboard, with VRse or the NYTimes VR app, the video flicks or jumps every other second. It's as though it was not stable. If I don't use the cardboard, watch them in one full screen it all goes fine.
Any idea?
Click to expand...
Click to collapse
I find when using any app i have motion (jitter) issues. The only place where i find it works well is in youtube.

I also have issues with it, my view keeps floating left

overheat in my z2
My z2 overheat when i used google cardboard, Does anyone this happens ?

I have a LG G Pro 2 phone (5,9"), I must create a QR code spécific to my cardboard for my large screen.
I Can only use VR app with calculate distorsion because full screen apps which only have splite screen doesn't work.

Screen moving constantly to the left
Has anyone managed to solve the above problem with screen jittering to the left when viewing 360 videos or in VR apps on the z2? Any luck. Is it a sensor related problem? Will recalibration of the sensors help?

Do it work on Xperia c5

Proximity Sensor and Screen

This information is for Version 3.0 of the application Proximity Sensor and Screen by Steven Stanley Bayes.
This application allows to really and virtually disable the proximity sensor while in calls, made and received and to re enable at will. This application does not require any third party software in general. However, only one menu selection, which really disallows the proximity sensor when in calls, made or received, requires XDA Framework and Xposed Installer and Xposed Jar. The application will work without these too.
There are no specific installation instructions. The application can be downloaded from GooglePlay : https://play.google.com/store/apps/details?id=stevenstanleybayes.proximitysensor in a standard way.
The application can also be downloaded from the posted in this information link. Then, the application APK file will be downloaded to the device's Download or Downloads folder and the user must go and manually click the APK file in order for the application to be installed on the user's device.
There are many more web sites where the application is available for download.
This application allows the user to make and receive calls with proximity sensor disabled and or or directly with speakerphone powered thus the proximity sensor will not power the screen down. This application also allows the user to select the proximity sensor to control the screen. The screen can be selected to be always powered or not.
When the speaker when in call is chosen, all calls made and received will be made with a powered speakerphone and the proximity sensor will not power the screen down when a call is made or received. The volume of the speaker can be adjusted to preserve battery energy. The device can be put in a zip bag and run while in the zip bag without taken out. This is great for wet weather and in a dusty and unfriendly environment. This also is a great health and personal hygiene option as the device will not be contaminated by ear wax and other sources of contamination and bacteria.
When proximity sensor control is chosen, the screen of the phone powers down when there is an object close to the proximity sensor. Thus, the screen will automatically power down when the phone is put in the pocket or put screen down on the table. This works regardless whether the user has chosen to keep the screen to be always powered or whether the screen is normally controlled by the OS. When the phone is away from and object, the screen powers automatically unless the screen has previously been powered down not by the proximity sensor but by other means, such as the OS or a press on the Power Button.
When the screen has been chosen to be always powered, the user can use the phone as a flash light which can easily be turned on by, say, placing the phone close to the chest. This way, the user can shine light for a while to see around, then, quickly stop the light and then, whenever needed, to quickly turn the light on again with just a movement of one hand and not by the power button although the power button will also work as set up. This way, the user would save battery energy as compared to constantly flashing light which may not be needed. The power button still works but the proximity sensor, when used as a switch, is easier to use than the power button.
More information is available in the application.
XDA:DevDB Information
Proximity Sensor and Screen, Tool/Utility for all devices (see above for details)
Contributors
StevenStanleyBayes, Rovo89, StackOverflow and XDA as well as other forums
Source Code: http://www.steven-stanley-bayes.com/ProximitySensor.apk
Version Information
Status: Stable
Created 2015-08-16
Last Updated 2015-08-17

Proximity Sensor and Screen Version 3.0 APK
Attached is the APK file of Proximity Sensor and Screen Version 3.0 APK for one click downloads from this post.

Attached is Version 4.0 of the application which offers a new interface as well as a shaker control of the screen with the accelerometer.
Version 4.0 of this application allows to really or virtually disable the proximity sensor while in calls, made and received and to re enable at will with a click and without restarts. This application also implements a shaker control of the screen as well as a proximity sensor control of the screen. This application does not require any third party software in general. However, only one menu selection, which really disallows the proximity sensor when in calls, made or received, requires XDA Framework and Xposed Installer and Xposed Jar. The application will work without these too.

man, can u tell me if u can implement or do u have any idea how to enable check proximity sensor and disable power button while is in pocket ? thank you

op3n said:
man, can u tell me if u can implement or do u have any idea how to enable check proximity sensor and disable power button while is in pocket ? thank you
Click to expand...
Click to collapse
This application will allow you to use the proximity sensor as a switch : when you put your device in your pocket, the screen will be powered off.
The best place to download the newest version of the application is : https://play.google.com/store/apps/details?id=stevenstanleybayes.proximitysensor&hl=en

StevenStanleyBayes said:
This application will allow you to use the proximity sensor as a switch : when you put your device in your pocket, the screen will be powered off.
The best place to download the newest version of the application is : https://play.google.com/store/apps/details?id=stevenstanleybayes.proximitysensor&hl=en
Click to expand...
Click to collapse
thanks Steven, but i already have xposed additions options; i observed that any app which will be installed even if is a module for xposed will drain battery bcs must stay all period waked. i have right? for that i search a script or somthing to implement without be an app. do u have any ideas?

In order to use the proximity sensor as a switch, of course, the proximity sensor must be on in order to detect any changes. Hopefully, the proximity sensor should not take too much power, however, the proximity sensor emits energy in order to evaluate the reflected energy, so, yes, there would be some energy consumption.
There is no physical way to use the proximity sensor as a switch and not to consume energy. Ideally, the programmer would be able to adjust the sample frequency and sensitivity but neither Android nor some device manufacturers are so smart.
Hopefully, the other sensors are off when not used. I do not recall to have used other sensors when not selected on the menu but I may have because the manufacturers and the Android have not made the proximity sensor control very reliable and I have experimented with many methods to trick the Android to ensure reliable way of the proximity sensor control.
Android may keep all sensors awake when only one is used but I do not have control over this.
A way to minimise the energy consumption is to use the accelerometer shakes as a switch. The application allows this. However, this is risky because any similar shake, such as bus ride, bicycle ride, etcetera, can be mistaken for such.
The only way I can think of to do what you ask without theoretical energy consumption is to use the light sensor ( photodiode ( s ) ). However, in case you use so, then, in the evening and night, the light sensor would think the phone is still in your pocket when not because there is not enough light. Also, light can penetrate through your clothes and very strongly through thin cotton, so, to even try to play with level adjustment may be unreliable. This is why I have not implemented the light sensor and I am not even happy with the not so high reliability of the accelerometer but I have decided to use the accelerometer with many levels of sensitivity.
I do, however, think Android would not use the proximity sensor constantly and would have a very low sample frequency of the proximity sensor data and thus there will not be very high energy consumption, definitely, the energy consumption of the proximity sensor would be negligible as compared to the huge consumption of the colour screen, so, you will add another few percent every 24 hours : not so much. Also, you do not need to run this continuously but only when you are mobile. When you are at home or work, you do not need to run the proximity sensor as your device usually stays away from you.

Another possible way to slightly lower the consumption is to programmatically switch the proximity sensor on for, say, 100ms and, then, to switch the proximity sensor off for, say, 100ms which the previous status of the screen is kept. This would reduce the energy consumption, but, I am not sure whether Android would switch the proximity sensor off immediately upon request.