On the Lumia 800 & 900 you could type in ##634# in the dialler and would get Nokias field test, This does not work the same on the 820 well at least on my one CV-O2-UK RM825, All that is displayed is the colour and life timer, Does anyone know of the new code for field test please? Thanks in advance
It's easy
##3282#
See the original topic
http://forum.xda-developers.com/showthread.php?t=1627548&nocache=1
Thanks I know that one, I wanted the one where you get to test all the phones functions ie: proximity sensor.
AndyFZ1S said:
Thanks I know that one, I wanted the one where you get to test all the phones functions ie: proximity sensor.
Click to expand...
Click to collapse
Yep that would be good if someone knows the code for the service menu
Sent from my RM-825_eu_euro1_217 using Board Express
There is no ODDT (diagnostic) on WP8 Lumia's.
Curious.
##3282 + call brings up Field Test on my 820.
Think it's called Diagnostics ##634#
Does yours show ALS values Proximity sensor and Battery info? As well as Camera, Audio loopback, Touch and Vibra tests?
Related
Anyone know of a tweak for this? On my sprint TP it is automatically turned off if I take picture while on a phone call, so there must be an option somewhere to turn it off for good.
i would really like to know this as well
ltt002 said:
i would really like to know this as well
Click to expand...
Click to collapse
Strange that it gets turned off during a phone call. Can anyone else confirm this?
yeah i tried it during a call and it does get turned off during a call.
i want to turn it off because the autofocus takes so long. especially when i need to snap those quick pictures...
Same here, no autofocus during a phone call... I'm using original ROM.
I'm very interested too in a solution for that strange behavior.
I would like to know how to turn it off as well because it takes too long to snap the shot! Would be great if there was an option to turn it on or off!
May no be EXACTLY what you're looking for, but go in to camera->settings->advanced and on page 3, there's a Shoot Option. Change this to Full Press, and no more AF.
dew.man said:
May no be EXACTLY what you're looking for, but go in to camera->settings->advanced and on page 3, there's a Shoot Option. Change this to Full Press, and no more AF.
Click to expand...
Click to collapse
I have it at Full Press, but that still is auto focus. As soon as you hit it, you will see the camera try to focus on what ever you're trying to shoot before it actually takes the photo.
I too am curious as to how to turn it off.
there's gotta be like a registry tweak????? someone? anyone? haha
Auto Focus - turn off tweak
ltt002 said:
there's gotta be like a registry tweak????? someone? anyone? haha
Click to expand...
Click to collapse
Even i m in dire need of this tweak........sometimes its impossible to get a good snap, bcos of the delay caused by auto focus.......
i was using UIQ 3 phone earlier, where a half press would lock the focus and full press will immediately click snap without a delay.....
can someone make sum tweal on similar lines
please someone. haha
BUMP.......
Turning off Auto Focus
Anyone help !!!!!!!!!
Bump
This is very odd. I guess that even HTC knew that the camera program was either not optimized or demanded to much resource so they cut off the autofocus mid call.
From my own experience, its really hard trying to figure out the system calls coming form the dialer, i dont think this is going to be an easy fix.
Bump!
Bump!
Bump!
it would be nice if someone could do this? i would donate happily )
also id really like a auto lfash - which i think is in development
but this is a good idea as i agree it takes so long to focus that you hardly ever get a good shot
I'm interested in this. Have missed many pics due to the focus being so slow!
why does nobody want to reply to thread with an answer? strange seeing as there is so much demand
I use AutoFocus and have no delay in taking a picture.
If you have a delay in taking a photo just change the settings using the Advanced Configuration Tool. Under the camera options, capture delay should be disabled, key delay disabled and capture key delay set to zero.
Also, try this:
HKLM/Software/HTC/Camera/Captparam/
and set
CaptureTimer = 0 (old=5000)
Two more things to do - go into the camera advanced settings (in the camera itself) and turn off the click sounds and set the review time to no limit. With those changes above I think I have a working camera here...
While we're at it, if your photos are yellow change the white balance settings: http://www.fuzemobility.com/?p=951
Continuing my quest of using the LED as flashlight for my new HD2, I updated TorchButton to support the HD2 as well.
Dropped your keys? Finding something behind the bench? Performing surgery on a computer and need to find that jumper on the mainboard?
This is a simple application built for some HTC devices that have a hardware LED, normally used to take pictures in the dark. However I found the LED to be perfect to be used as a handy pocket flashlight.
Usage
There is no GUI for this application. Just start TorchButton to enable the LED on the back of your device. Start TorchButton again to turn it off.
Check out the readme if you're an advanced user and wish to change some registry settings, i.e. to allow a longer maximum time the LED is enabled.
Known issues
- [Fixed] New icons are not working when TorchButton is installed to Storage Card
Todo
- Create an app to configure the registry settings
- See if support for Omnia Pro (B7610) is feasible (someone should send me the related dlls...)
- [Done] Add a seperate timeout for bright mode
- [Done] Add blink mode with bright led
- [Done] Use new icons provided by tnyynt
- [Done] Add support for Omnia (the one found here)
- [Impossible] See if it's possible to control leds seperately ('economic mode') Sorry, this is not possible. (Tech-talk: setting a single GPIO enables both LEDs. There doesn't seem to be a GPIO for each LED seperately.)
Wishful thinking
- Camera app to interpret the morse
History
Version 2.3
- Fix icons not showing in HTC Sense or WM 6.5 start menu when installed to Storage Card.
Version 2.2
- New icons for all TorchButton apps (thanks tnyynt!). These only work in WM6.5 and up. Older OS's will still see the old icons.
- Added registry setting to use bright setting in blink mode (see BlinkUsesBrightMode).
- Bright mode now has a seperate timeout, configurable in registry (see BrightModeTimeout).
- Added support for Samsung Omnia i9x0 devices (hopefully they all work). Thanks to raph/zemrwhite2/PaSSoA. Thanks to Chainfire for testing on his Omnia i900L.
- [edit] Shortcut names have changed. I found them nicer this way, no two-line icons. And the text is now also not cut-off when added as shortcut in the home screen.
- [edit] Improved handling of bright mode. It should stop immediately now when pressed again, instead of waiting for a 500ms interval. This makes BlinkUsesBrightMode possible combined with low intervals for blink mode.
- [edit] Soft-reset your phone after upgrading from an older version! Else the new icons will not show.
Version 2.1
- Bright mode is now support on the HTC HD2 (Leo).
- Added a one-time warning message when bright mode is used for the first time.
Version 2.0
- Initial version with support for the HTC HD2 (Leo) (bright mode is not supported on the Leo)
Version 1.x
- Support for the Touch Pro
Dont think about something. Untill i read your post. This could be handy sometimes. Thnx
Awesome man I was just thinking how I missed that
Btw what's missing for bright mode to work? If I'm not mistaken there is a brighter mode just before taking a pic.
Thanks! I was dissapointed that hTorch didn't work on the HD2 now I got this. Wonderful!
Great ! thanks
Have it on my Omnia and was hoping to have it for my future HD2 !
You're all welcome! Glad to hear you like it.
12aon said:
Awesome man I was just thinking how I missed that
Btw what's missing for bright mode to work? If I'm not mistaken there is a brighter mode just before taking a pic.
Click to expand...
Click to collapse
The mode is there, but it's not as easily called as it was on the Touch Pro. In fact I haven't found the API call at all yet. May need some hacking around the API to get that to work. The normal mode produces _quite_ the amount of light though, it's even more light than the bright mode of the Touch Pro thanks to the dual led.
Zero Masamune said:
Thanks! I was dissapointed that hTorch didn't work on the HD2 now I got this. Wonderful!
Click to expand...
Click to collapse
hTorch will work again once I update the C# wrapper to support the Leo, as hTorch makes use of my C# library. I'll do that somewhere in the upcoming week.
Great, works perfect ! Txs
Can anyone confirm this don't burn anything out? On the X1 the light modules weren't heatsinked properly and caused vibrator motor to screw up after 15secs use as a torch.
Thanks!
kinnyfaifai said:
Can anyone confirm this don't burn anything out? On the X1 the light modules weren't heatsinked properly and caused vibrator motor to screw up after 15secs use as a torch.
Thanks!
Click to expand...
Click to collapse
I can't confirm it won't ever burn out. However, realise that enabling the LED is actually the same as using your camera with the lights on in the dark. This _shoud_ be possible for prolonged times as well.
Were you using the 'bright' setting on the X1? (If that's possible there.) That might explain it better... otherwise you could just send in the device for repair, as it's normal use of the device. Especially if it's after only 15 seconds.
NetRipper said:
I can't confirm it won't ever burn out. However, realise that enabling the LED is actually the same as using your camera with the lights on in the dark. This _shoud_ be possible for prolonged times as well.
Were you using the 'bright' setting on the X1? (If that's possible there.) That might explain it better... otherwise you could just send in the device for repair, as it's normal use of the device. Especially if it's after only 15 seconds.
Click to expand...
Click to collapse
It was a known problem that the LEDs weren't heatsinked properly on the X1 and there was a huge warning on using hTorch. I've not installed hTorch and never used the LEDs on my X1 as a torch cos of this oversight by the manufacturer. I do miss being able to use the LEDs as a torch though, it's very handy.
Heej nice, i come from oud-Beijerland
nice app, but bright mode doesn`t work for me..
NetRipper said:
Continuing my quest of using the LED as flashlight for my new HD2, I updated TorchButton to support the HD2 as well.
Dropped your keys? Finding something behind the bench? Performing surgery on a computer and need to find that jumper on the mainboard?
This is a simple application built for some HTC devices that have a hardware LED, normally used to take pictures in the dark. However I found the LED to be perfect to be used as a handy pocket flashlight.
Usage
There is no GUI for this application. Just start TorchButton to enable the LED on the back of your device. Start TorchButton again to turn it off.
Check out the readme if you're an advanced user and wish to change some registry settings, i.e. to allow a longer maximum time the LED is enabled.
History
Version 2.0
- Initial version with support for the HTC HD2 (Leo) (bright mode is not supported on the Leo)
Version 1.x
- Support for the Touch Pro
Click to expand...
Click to collapse
20mihalko said:
nice app, but bright mode doesn`t work for me..
Click to expand...
Click to collapse
Isn't it clearly stated that brightmode doesn't work.......jeez....dude...read
ET said:
Isn't it clearly stated that brightmode doesn't work.......jeez....dude...read
Click to expand...
Click to collapse
sorry, my mistake
kinnyfaifai said:
It was a known problem that the LEDs weren't heatsinked properly on the X1 and there was a huge warning on using hTorch. I've not installed hTorch and never used the LEDs on my X1 as a torch cos of this oversight by the manufacturer. I do miss being able to use the LEDs as a torch though, it's very handy.
Click to expand...
Click to collapse
The vibrate function does not work at all on my X1 after installing and using hTorch. User beware..!
This is my next phone when O2 decide to put it on their shelves, and hopefully its built better than the X1.
Any chance of some source code?
I've been looking through the HD2 camera drivers, and have found a few things that should be the LED (can't test it as I have no device), but am wondering if it's the same method as yours!
l3v5y said:
Any chance of some source code?
I've been looking through the HD2 camera drivers, and have found a few things that should be the LED (can't test it as I have no device), but am wondering if it's the same method as yours!
Click to expand...
Click to collapse
Here are the important code snippets of the API that I'm using. The methods were pretty obvious (luckily).
typedef int (__stdcall *LEO_INIT)();
typedef int (__stdcall *LEO_SETCURRENT)(DWORD dw1);
...
LEO_INIT InitFlashLight;
LEO_SETCURRENT PMICFlashLED_SetCurrent;
...
hCamera=LoadLibrary(L"CameraPlatform.dll");
...
InitFlashLight = (LEO_INIT) GetProcAddress(hCamera, L"InitFlashLight");
PMICFlashLED_SetCurrent = (LEO_SETCURRENT) GetProcAddress(hCamera, L"PMICFlashLED_SetCurrent");
...
InitFlashLight(); // must be called before SetCurrent has any effect
...
PMICFlashLED_SetCurrent(0); // turns it off
PMICFlashLED_SetCurrent(1); // turns it on
There's also a PMICFlashLED_SetMode(x); but I haven't been able to figure out what it does. As far as I could see when disassembling it wants one parameter.
If you have any ideas on the bright mode, they'd be more than welcome. If you want the full source to make some modifications or to toy with it, let me know.
NetRipper said:
Here are the important code snippets of the API that I'm using. The methods were pretty obvious (luckily).
typedef int (__stdcall *LEO_INIT)();
typedef int (__stdcall *LEO_SETCURRENT)(DWORD dw1);
...
LEO_INIT InitFlashLight;
LEO_SETCURRENT PMICFlashLED_SetCurrent;
...
hCamera=LoadLibrary(L"CameraPlatform.dll");
...
InitFlashLight = (LEO_INIT) GetProcAddress(hCamera, L"InitFlashLight");
PMICFlashLED_SetCurrent = (LEO_SETCURRENT) GetProcAddress(hCamera, L"PMICFlashLED_SetCurrent");
...
InitFlashLight(); // must be called before SetCurrent has any effect
...
PMICFlashLED_SetCurrent(0); // turns it off
PMICFlashLED_SetCurrent(1); // turns it on
There's also a PMICFlashLED_SetMode(x); but I haven't been able to figure out what it does. As far as I could see when disassembling it wants one parameter.
If you have any ideas on the bright mode, they'd be more than welcome. If you want the full source to make some modifications or to toy with it, let me know.
Click to expand...
Click to collapse
That's what I'd come to as a conclusion, so glad that works!
Is there any need to un-init the flash light?
PMICFlashLED_SetMode will probably need some playing around, though might enable your "bright" mode. Will have a play with that when I get an HD2!
l3v5y said:
That's what I'd come to as a conclusion, so glad that works!
Is there any need to un-init the flash light?
PMICFlashLED_SetMode will probably need some playing around, though might enable your "bright" mode. Will have a play with that when I get an HD2!
Click to expand...
Click to collapse
There doesn't seem to be an un-init function. However, the debug console shows that it detects when the DLL is being attached to or detached from, so there's probably some cleanup code there.
I also haven't found any side-effects yet. TorchButton works fine even when the camera app is running. They don't interfere with eachother (other than toggling the LED to their own behalf). On the Touch Pro it wasn't possible to run TorchButton and the camera app at the same time. Not that I ever wanted to, but still.
In regard to that mode function. It must be for something. I tried using it in various ways already but it didn't matter. Maybe you'll have more luck
might be confused right now, but seems that when in camera mode, and battery is below 50% you cant use the flash - anybody know if this will affect the app?
haven't got my hd2 yet so cant help you out, but there's a thread under the Leo -- > Leo sub-forum
cheerios!
I resolve the HD2 problem for proximity sensor bug during call with this steps:
1. turn off vibration for connecting (go to dialer menu)
2. turn off dialer keypad sound (via HD2Tweak 1.2)
3. install Touch in call screen tweak 1.2
Hi !
Could explain a little bit the "proximity sensor bug during call" you're facing ?
Which ROM verison are you using ?
thanks a lot !
papagon said:
Hi !
Could explain a little bit the "proximity sensor bug during call" you're facing ?
Which ROM verison are you using ?
thanks a lot !
Click to expand...
Click to collapse
When I dial , the screen go off without any association with proximity!
both original & energy ROM
Hi !
Thanks for your answer...
My problem is slightly different, but involves radio ROM and winmo drivers, because everything was fine with stock ROM 1.48.406.1 and radio ROM 2.15.50.14.
Now that I'm using the stock ROM 3.14.406.2 (wich includes radio 2.15.50.14)
when i'm in a call, the screen stays off even if the phone is no longer on my ear...
So that's why I as interested by your solution, but it does nothing on my phone...
With this last official update from HTC, i'm now facing keyboard sensitivity issues (everything was alright with prévious ROM and HTC patch for the sensitivity), and this proximity sensor problem...
i find the case can make the sensor play up as most manufacturers dont account for the sensor
jonpickles70 said:
i find the case can make the sensor play up as most manufacturers dont account for the sensor
Click to expand...
Click to collapse
please explain more.
manufacturers dont put cut outs on cases or they arent big enough so the sensor is then covered
Greetings from an Android newbie, (coming from a Nokia 3210 )
I got a Xtreamer Aiki 5, and noticed that the proximity sensor is defective.
Rom version 10.1
Internet learned me to download the apps Android Sensor and Hardware disabler.
Android sensor gives the following:
name : tmd2771 proximity sensor
vendor : Capella
version : 1
power : 0.13
max range: 1.0
resolution : 1.0
Hardware Disabler should be able to disable the driver of the proximity switch, but there are so many
drivers listed.
Does someone know the name of the driver which have to be disabled?
Go to the play store and search for a program called "proximity sensor calibration". Install it, follow the instructions and most likely all works well again for you.
I have installed and run the app, but i only get the message:
Rezound Proximity Sensor Calibrator is not responding.
Would you like to close it?
Even after a reboot same thing happens.
Is there another way to let the screen 'on' during calls (and skype) as well?
( app Screen On doesn't work on it )
thaineth said:
I have installed and run the app, but i only get the message:
Rezound Proximity Sensor Calibrator is not responding.
Would you like to close it?
Even after a reboot same thing happens.
Is there another way to let the screen 'on' during calls (and skype) as well?
( app Screen On doesn't work on it )
Click to expand...
Click to collapse
Well, there is another program named "Sensor Kinetics" which might help and works on my Xtreamer. At least it shows the possibilities of the proximity sensor: There are only two states with Xtreamer (which is 0 and 1), you can't measure exact distances.
If you still see a problem I'd advise to reflash your ROM. Usualy that helps...
AP756 said:
Well, there is another program named "Sensor Kinetics" which might help and works on my Xtreamer. At least it shows the possibilities of the proximity sensor: There are only two states with Xtreamer (which is 0 and 1), you can't measure exact distances.
If you still see a problem I'd advise to reflash your ROM. Usualy that helps...
Click to expand...
Click to collapse
It took me some time, but i have done both of the recommendations.
Flashed the ROM and installed Sensor Kinetics. But no luck. When SK is started, there is no line in the graphic at all.
(found how it should look like on the website of that program).
It is for surenow that the proximity switch is defective, other programs give the same result as well.
Is there a way to change or disable the drivers of that switch, so the screen will stay on bright during telephone calls or skype calls?
Does someone know the name of the specific driver?
thaineth said:
It took me some time, but i have done both of the recommendations.
Flashed the ROM and installed Sensor Kinetics. But no luck. When SK is started, there is no line in the graphic at all.
(found how it should look like on the website of that program).
It is for surenow that the proximity switch is defective, other programs give the same result as well.
Is there a way to change or disable the drivers of that switch, so the screen will stay on bright during telephone calls or skype calls?
Does someone know the name of the specific driver?
Click to expand...
Click to collapse
I just wonder, is this still the good place at the forum to put this question, or should it be transfert to a more technical part?
I don't know where to ask other than here, about this problem,
I got my OP6 and installed whatsapp and I am now trying to activate web whatsapp which requires you to scan a QR code on a web page on your computer.. However the camera is not focusing and therefore recognising the QR code. If I try to take a picture in a whatsapp chat it shows a very clear picture.
I've added a screenshot of what this looks like. I tried pressing the screen, double tapping, rebooting etc. I use a custom ROM, Havoc.
By moving fingers over the two lenses I've figured out that whatsapp is using bottom of the two lenses present lens for finding QR code.
Is this a hardware problem? Or is there something else going on? Can I test this somehow? I am not sure how I can just test this one lens alone.
Thanks in advance for any help!
EDIT: I did read up on all the camera problem threads but it seems my problem is just with the lower lens hence this thread.
I just checked with a supermarket app that allows you to scan their items and here the scan camera focused quickly and perfectly.
roel1976 said:
I got my OP6 and installed whatsapp and I am now trying to activate web whatsapp which requires you to scan a QR code on a web page on your computer.. However the camera is not focusing and therefore recognising the QR code. If I try to take a picture in a whatsapp chat it shows a very clear picture.
I've added a screenshot of what this looks like. I tried pressing the screen, double tapping, rebooting etc. I use a custom ROM, Havoc.
By moving fingers over the two lenses I've figured out that whatsapp is using bottom of the two lenses present lens for finding QR code.
Is this a hardware problem? Or is there something else going on? Can I test this somehow? I am not sure how I can just test this one lens alone.
Thanks in advance for any help!
EDIT: I did read up on all the camera problem threads but it seems my problem is just with the lower lens hence this thread.
Click to expand...
Click to collapse
The lower lense isn't for capturing images.
mikex8593 said:
The lower lense isn't for capturing images.
Click to expand...
Click to collapse
But if whatsapp forced the use of this lens on OP6 more people would have seen this issue? Can you try it perhaps. No need to scan, just activate the camera: open Whatsapp > three dots at top right > WhatsApp Web.
Thanks!
roel1976 said:
But if whatsapp forced the use of this lens on OP6 more people would have seen this issue? Can you try it perhaps. No need to scan, just activate the camera: open Whatsapp > three dots at top right > WhatsApp Web.
Thanks!
Click to expand...
Click to collapse
I don't use that app.
Whatsupp?
Have u tried cleaning the lens?
I had the same issue but it was when installed omni rom.. i have played with it a bit flashed back oos, and it working properly.
I have same problem, but i use custom rom, liquid_remix.
Has anyone got the solution?
mikex8593 said:
The lower lense isn't for capturing images.
Click to expand...
Click to collapse
yes it is, open the camera and place your finger on the lower lense and you will see that no image can be captured. Upper lense is depth sensor also a camera with autofocus.
if you want to test the cameras dial *#*#1597#*#* and you can change wich of both cameras you want to use to take pics. (at least in oxygenOS, i dont know about other roms). to discard a hardware malfunction, propper way to test this is to install stock OOS, then dial that number and check if both cameras focus (point at a distant object and see if it is focused, then place your hand close to the camera and see if it can focus on it) and check if OIS work (activate the camera and move the phone and look at the camera if it moves with the phone or if it stabilizes correctly)