Hi,
For two days, I have the autofocus of the camera that works all the time in standby mode only This is "click" at regular intervals
Including when I reboot, I hear just before you see the first screen of boot ...
By cons, as soon as I leave the standby mode before, no problem except that the camera is no longer the point, the autofocus does not work ...
And really weird is that this "click" I think varies according to the occupation of the CPU because if I leave an application running and I goes to sleep, I do not hear it!
I made a task29, wipe all over the place, install new rom, and also an original rom ... Even removing the phone to see if something was not disconnected but I have not found.
Do you have an idea how to cope ?
Or maybe a way to reset the memory lowest level because I think it is software, not hardware (well I think).
Thank you to those who can give me help.
Regards.
good post
good post
lol
Always the same problem with a fresh install of sense 3 with last kernel of Rafpigna...
no one has ever had this problem of noise camera in standby mode or to boot the phone?
Is it possible that this is a hardware problem?
What is really strange is that as soon as I get out of standby mode, the noise stops! And when I want to take a picture, the autofocus does not work ...
Task29 can't help me... Always the same issue... I tried WM7 I know it's sad but it does not change (I did not expect less).
No one can help me ??
...saw a post of a xda member with the same issue on the typhoon some months ago.
He made a video:
http://www.youtube.com/watch?v=46hRUY89A0E
..do youve got the same issue?
will it also autofocus all time when you dont got a rom installed?
Hi j4n87,
This is exactly the same problem, I can see the lens moving like that...
this is just since a week. it worked fine before !
This is after installing a version MIUI (when I had already installed several versions before without problems).
I try everything but I can not recover the normal operation of the camera.
Can you help me more ??
Thank you.
Regards.
j4n87 said:
...saw a post of a xda member with the same issue on the typhoon some months ago.
He made a video:
http://www.youtube.com/watch?v=46hRUY89A0E
..do youve got the same issue?
will it also autofocus all time when you dont got a rom installed?
Click to expand...
Click to collapse
I found that if I put in airplane mode, so no use of radio, there is no noise of the autofocus ...
I will try to degraded version of the radio to see if it changes something.
Alas no, it does not change, still the noise of the camera.
RESOLVED...
yay it works thanks to Dimension2035 (thank you very much for his invaluable help).
This is what to do:
- To MAGLDR
- Download the version of tytung
- Make the phone operational by using a little (there is always noise)
- Remove the battery overnight: miracle, everything works.
I'm really happy.
Here is the solution.
Regards and again thanks to Dimension2035
manu33xtro said:
I found that if I put in airplane mode, so no use of radio, there is no noise of the autofocus ...
I will try to degraded version of the radio to see if it changes something.
Alas no, it does not change, still the noise of the camera.
Click to expand...
Click to collapse
Related
how come the camera on the XDA is horrible, its grainy and dark... i tried adjusting the settings but then after i closed and reopened the camera quality was back to being bad again. is there a fix for this or is that how the camera is.
I mainly use the night mode indoors and save the auto mode for outside. Make sure you work out the settings with your computer; the best pictures on the PDA aren't always the best on the computer and vice-versa.
Oh yeah, I don't think you can make most of the settings stick other than the auto/daylight/dark etc. mode.
I have another problem with my camera...
When i take a shot, the image displayed in the viewfinder before capturing, is perfectly lit with the right brightness-contrast etc.
But when i capture an image, it brightens it up until the image bleeds, and its terrible....I tried to adjust different settings, but it still did the same.
Its good for night shots, but during day time, i get 80% of my pixels completely white!
Not too bothered, as the camera is actually pointless for me....and besides, i'm not the "take pictures often" kinda guy!
San
read my camera tweak topic.
try CoolCamera
http://www.ateksoft.com/files/CoolCameraTest.zip
i found turning off 3g, and using gsm has helped a lot with all aspects of my phone. the camera looks a LOT better compared to a week ago when it was on 3g. back then, i thought it was completely unusable..thats how bad the quality was. and i had tried night time mode indoors, and it all jjust came out blurred
where's the camera tweak post? i'm starting not to like this phone, there is way to many tweaks and changes that have to be done to it just to make it an 'ok' usable phone.
el_illumbrato said:
i found turning off 3g, and using gsm has helped a lot with all aspects of my phone. the camera looks a LOT better compared to a week ago when it was on 3g. back then, i thought it was completely unusable..thats how bad the quality was. and i had tried night time mode indoors, and it all jjust came out blurred
Click to expand...
Click to collapse
how do you turn of 3G?
thats strange the camera seams fine to me i havent had and of the note problems
alix776 said:
thats strange the camera seams fine to me i havent had and of the note problems
Click to expand...
Click to collapse
What ROM version are you using? We are all referring to the latest I-Mate and QTEK ROM. You might be using the old version of O2 which does not have those pixel dots.
dreamtheater39 said:
When i take a shot, the image displayed in the viewfinder before capturing, is perfectly lit with the right brightness-contrast etc.
But when i capture an image, it brightens it up until the image bleeds, and its terrible....I tried to adjust different settings, but it still did the same.
Click to expand...
Click to collapse
In these days i'm using camera and i have this problem, is there a solution???
If anyone is still there I havve a problem. When I tried to update it. i think it failed and got stuck on the serial v1.00 botloader. Luckily I found a way to fix that. May one of you please supply the 1.30.79 WWE QTEK-TMobile rom please I cannot find it. Also I ahve a 4gb that's not working with my device. Could it be possible that my rom is to old and the update for 4gb cards haven't been set in place fo r that rom? This the only time I've heard of a 4g card not working. Please help. I think its a 2005 rom
Hello to everybody.
I have rom 1.48 and some programs installed (BsB and net 3.5 above all plus some games). I installed also the hotfix for the camera but now my xenon flash seems to be dead. When I turn on the camera, the flash butto remains always off even if I try pressing the flash button. I don't think it's a hardware problem but software or maybe registry because if I use TorchButton program, the leds are working properly (bright, SOS and so on).
I there anybody able to help me?
I thank you in advance and thanks to ALL the mebers of XDA.
All the best.
Is your battery low? I know the flash gets turned-off when the battery is low.
it was above 10% (the first warning level). but after your advice I will try again when is above 50% at least and I will post here...
Diamantes said:
it was above 10% (the first warning level). but after your advice I will try again when is above 50% at least and I will post here...
Click to expand...
Click to collapse
I think the flash stops working @ 30% battery level.
phew...!!!
ok guys, everything is gonna be alright....
I waited patiently and checked every 1% step up on the battery level...
Below 20% the flash is automatically turned off...
thanks to all for the quick replies..
bye
so not a problem or issue but speaking of camera flash, does anyone know if theres a program to use it as a flashlight only? i mean, i could always open up the camera program and turn it on from there...
search in the forum for TorchButton program... it works perfectly
Does it ? It does not work on mine ..
Oh .. there is a new version, which works !
http://forum.xda-developers.com/showthread.php?t=581382
Hello i have this problem while video recording the image gets stripes trough and just flickers cross the screen than its visible in playback and it gets stuck after 2 secs but sound keeps on going! it happens all the time! what can i do?
can i reinstall that camera app or something? picture taking is fine! some help please! =)
I get a similar issue occasionally when taking video. Half the screen (usually the bottom half) will be green with lines through it for the first 1 or 2 seconds before everything becomes normal.
The android video recording never does this for me, so I assume its a bug with the manilla camera software.
hmm strange... any solution for it yet? iv tryed the pink fix maybe i thought i could handle the fix for it too but it didnt =/... grrr..
sigh....i get the same darn thing!
Could this be a corrupted driver for camera? can we try few drivers see what happens! maybe it would work!
Which Radio Roms are you all using?
The radio Rom also controls the camera, perhaps changing it will help you with your problem.
Wilco said:
Which Radio Roms are you all using?
The radio Rom also controls the camera, perhaps changing it will help you with your problem.
Click to expand...
Click to collapse
You.
Are.
Perhaps.
A genius.
I was just thinking about this very thing. Since I had to flash a new radio when I installed android (went from 2.06 to 2.12) I have NOT had any glitches in video recording. I was just going through some of my recent videos and they all look perfect (including all the ones taken in WinMo.)
/solved
good call Wilco
Could some 1 tell me where can i find the NEWEST RADIO! and do i need to flash hardSPL3 to use it? im still kinda lost in this :/...
Newest radio? You should probably read THIS thread. The best radio for you is not necessarily going to be the "newest" one.
interesting i just flashed a new rom athemis v33 and 2.12 radio and now all is fine! seems the rom has made me trouble! i left the radio on 2.12 :/... complicated stuff haha
Hi
I have a HTC HD2
and i installed andriod nand rom on it with the following things
HSPL 2.08
Radio 2.15.50.14
MAGLDR 1.12
i installed almost 10 andriod roms and find the same problem
after making or receiving a call screen goes into black screen and hangs up. i have to reboot the device by removing the battery. i would appreciate if any one can provide me the solution to fix this problem as i love andriod roms.
thank you
mohammedmazher said:
Hi
I have a HTC HD2
and i installed andriod nand rom on it with the following things
HSPL 2.08
Radio 2.15.50.14
MAGLDR 1.12
i installed almost 10 andriod roms and find the same problem
after making or receiving a call screen goes into black screen and hangs up. i have to reboot the device by removing the battery. i would appreciate if any one can provide me the solution to fix this problem as i love andriod roms.
thank you
Click to expand...
Click to collapse
I am facing this only when battery is bellow 15%. If this is the case then just charge it before it goes to 15%.
If that's not the case then you can try installl MAGLDR v1.3
Do you have this issue in Froyo or Gingerbread ROMs? or in both? What version of CWM are you using?
I have the same problem on MIUI since after approximately 1.3.18 (cutover from Froyo to Gingerbread). Also have this problem on CME DHD2 Compact.
It is also an issue if someone tries to call me.
Sometimes, if I try waking the phone from sleep (power button) and it hits the black screen, and I wait long enough, it will wake. But again, the only real fix I know is pulling the battery.
I am running MAGLDR 1.13
Also, another fix that works sometimes is plugging in the phone into a power source e.g. laptop USB port
It's something about light sensor, when you put your screen into a strong light it would be turn "unblack" again. I don't know how to fix it, is this a problem with this hardware because it's broken or my version of LEO doesn't support NAND full functionaly.
Begging for answer!
i know about my poor english
I have this problem too.. running latest Hyperdroid rom by pongster (magdlr version) and it's driving me crazy. Sometimes phone wakes up normally after a call like it shoud, sometimes is stuck with black screen for few minutes, hours even (although i can't wait that long so i pull out battery)..
Back on WinMo everything worked normally, so it's not an hardware issue with proximity/light/whatever sensors
Is there any fix out yet? I googled and searched this forum a lot and haven't found nothing much helpful, ony a couple of threads with bunch of people with same problem like me. An option for disableing those sensors would be just as good, i've tried few apps for keeping the screen awake and none of them actually worked..
Any help is appreciated.. thanks in advance.
Bump!
Anyone? :/
I have the same issue - running Gingerbread, MAGLDR 1.13
Very annoying cause everything else works super.
Temporary solution i use is to use headset / handsfree. Then there is no problem.
So experts on XDA, we are begging for a fix for this!
I have the same issue since first Android roms and never found a real solution for the problem.
Instead i found a bypass that works for me reasonably well (99% of the cases the screen turns on after a call).
I installed the following 2 applications that wakes up my screen after the call (install then enable each one):
1. Screebl - https://market.android.com/details?id=com.keyes.screebl.lite
2. Modified version of SpeakerShake - http://forum.xda-developers.com/attachment.php?attachmentid=449922&d=1290758421
I suspect this issue is somehow related to hardware failure in light sensor. Installing these programs solve this problem for me.
Also take a look on the following thread:
http://forum.xda-developers.com/showthread.php?t=835127
I have had the same thing happen to me but only around 2 or 3 times in a about 3 months of usage. Had it on both CM7 and MIUI Gingerbread ROMs regardless of battery percentage.
MAGLDR 1.13
Some users experience this using SetCPU
if you have a profile for screenoff and it's set to the lowest frequency, try to set the frequency to something above 500 MHz.
If you have smartass set as governor, then even setting the frequency to it's highest (without OC) during screenoff wouldn't change anything in battery performance, but the device will wake up faster.
Your setup works for me as well - until we`ll see a fix for it this will do
Quiethinker said:
I have the same issue since first Android roms and never found a real solution for the problem.
Instead i found a bypass that works for me reasonably well (99% of the cases the screen turns on after a call).
I installed the following 2 applications that wakes up my screen after the call (install then enable each one):
1. Screebl - https://market.android.com/details?id=com.keyes.screebl.lite
2. Modified version of SpeakerShake - http://forum.xda-developers.com/attachment.php?attachmentid=449922&d=1290758421
I suspect this issue is somehow related to hardware failure in light sensor. Installing these programs solve this problem for me.
Also take a look on the following thread:
http://forum.xda-developers.com/showthread.php?t=835127
Click to expand...
Click to collapse
Yup, this worked for my setup to - thanks!
hi guys ! i can`t realy figured out how to set it . shall i use only one app or both ? and wich settings should be ?
xanthrax said:
hi guys ! i can`t realy figured out how to set it . shall i use only one app or both ? and wich settings should be ?
Click to expand...
Click to collapse
(install then enable each one):
Click to expand...
Click to collapse
Incearca Sanity app, cauta pe Market, mie aceste doua nu mo ajutat
with me is so but only if I navigation (Navigon) and to have someone call me and then left the screen black and I can not make
try to change the kernel. that works for me
hey guys! i found the solution goin through the market!
download an app called "Sanity" theres a free version in the regular android market.
go to the settings > general > check "Reverse Proximity" (This will give you some warning about not using it if you DONT have a buggy proximity sensor). Check it anyways. Then go back to preferences then click "Proximity" scroll down and uncheck Turn off screen and leave leave the Turn on screen checked. this will force your phone to stay on during calls so that it never has to go through the proximity phase of calls this no more black screens. Hope this was helpful ^_^
Thanks!
I had this problem aswell. MIUI & Cyanogen mod were the ROMs I was using, and this problem started occuring after a few months use (my screen is also damaged from a fall, so maybe the sensors are a little damaged as well).
When I installed the WinMo 6.5 stock ROM again, everything was normal, except that my screen still turns black during calls BUT I can activate it again by pressing the power button.
Now I installed android again and the Screebl app (enabled it) and I have the same functionality! The only problem that remains is that my screen still turns black during calls, so I have to answer with the phone button and putt down phone with the power button. Still beats having to remove the battery though .
If someone has a fix for the black screen, it would be more than welcome!
But, thanks a million for the Screebl app tip! I can use my phone again .
papaganz said:
Thanks!
I had this problem aswell. MIUI & Cyanogen mod were the ROMs I was using, and this problem started occuring after a few months use (my screen is also damaged from a fall, so maybe the sensors are a little damaged as well).
When I installed the WinMo 6.5 stock ROM again, everything was normal, except that my screen still turns black during calls BUT I can activate it again by pressing the power button.
Now I installed android again and the Screebl app (enabled it) and I have the same functionality! The only problem that remains is that my screen still turns black during calls, so I have to answer with the phone button and putt down phone with the power button. Still beats having to remove the battery though .
If someone has a fix for the black screen, it would be more than welcome!
But, thanks a million for the Screebl app tip! I can use my phone again .
Click to expand...
Click to collapse
I also try with WinMobile and the problem was still there ...
I think the sensor is broken ....
I will bring my phone to service ... and when i take it back I will tell you whether it is repaired
Solution
I had the same problem with Android roms on my HD2. I saw in an other thread a member (z-o-r-r-o-, thanks btw) wrote "just clean dust on the screen, where sensor is situated". This looked like a joke to me, but it's not. On a review of the phone I found the place of the proximity sensor. This is on the top of your screen next to the speaker, on the left if you look at the screen. I just took off the protection layer of the screen and cleand the sensor and the problem was solved. So I cut of a bit from the protection layer so that the sensors arn't touched by anything.
I think the problem is that this sensor is much more sensitive with android roms.
Hope this works for you to.
Hey,
I have a major problem for a couple of weeks now. My phone just keeps waking up randomly and turns the screen on by itself. I have root and s-off and tried out a few roms. Sense Roms as well as MIUI roms... It does not make a difference at all, so I guess it can't be rom related. I have read a few more posts on the web of users having a similar problem but there was no solution given anywhere.
Also, my speaker automatically turns on when I receive or make a call. These two problems seem interconnected since there is at least one person on xda having exactly the same two issues...
Does anybody have an idea or a solution for this? I would be thankful for any kind of help! Thank you in advance!!!
I've a similar problem a bunch of months ago, my phone turn on automatically, without no logic. I've resolved the problem pulling out the battery for a night, after that the problem disappeared.
I hope that will help you to resolve your problem,
Rodomar705
Thanks, I will try that out tonight and report!
Ok, I tried it out last night, but it did not work
Does anybody have a different idea?
Dabarr said:
Ok, I tried it out last night, but it did not work
Does anybody have a different idea?
Click to expand...
Click to collapse
Did you check the date and time once you'd insert battery inside DHD? I think to solve the problem that way, you should leave DHD without battery until the internal battery will be totally discharged. It takes approx. 12-14 hours, and you can be sure only if turning on DHD you'll find time and date set to 12:00am, 1st jan 1980 (or something like that).
Yeah, it definately worked though, time was resetted as well. I turned it in today, hope to be able to pick it up next week. Before, I ran the Ruu to set it back to shipping condition... It still had the same error, so it is definately not rom related...
It is a huge drag without it... Already feeling uncomfortable ^^
Dabarr said:
Hey,
I have a major problem for a couple of weeks now. My phone just keeps waking up randomly and turns the screen on by itself. I have root and s-off and tried out a few roms. Sense Roms as well as MIUI roms... It does not make a difference at all, so I guess it can't be rom related. I have read a few more posts on the web of users having a similar problem but there was no solution given anywhere.
Also, my speaker automatically turns on when I receive or make a call. These two problems seem interconnected since there is at least one person on xda having exactly the same two issues...
Does anybody have an idea or a solution for this? I would be thankful for any kind of help! Thank you in advance!!!
Click to expand...
Click to collapse
same here, i have the MIUI ROM, will try with another version.
Dabarr said:
Yeah, it definately worked though, time was resetted as well. I turned it in today, hope to be able to pick it up next week. Before, I ran the Ruu to set it back to shipping condition... It still had the same error, so it is definately not rom related...
It is a huge drag without it... Already feeling uncomfortable ^^
Click to expand...
Click to collapse
Sorry mate!! Just wait for a week, ist not so long time, and you'll get back your phone as new as when you bought first time!! Hope this makes you feel a little bit of joy!!
Ok, I have gotten my phone back on thursday (after one week)...
SO far so good, everything worked again, they even set the proximity sensor right again... Then I rerooted it and put another MIUI on it...
On friday then, I put Vipermod back in and undervolted it by 50 mA... BOOM, the issue came back, I couldn't remove it, so I took the battery out and waited for 12 hours, as you suggested... and it worked... Issue was gone... Then I ran vipermod again and BOOM the issue was there again... It didn't even help to set the mA values back to normal, I had to reset it again by taking out the battery for 12 hours.
So my conclusion is that this issue is directly related to the actual USE (not just the installation) of vipermod... Can anyone confirm? Don't want to put out false information in the vipermod thread without having others to confirm...
need help also
Stinger696 said:
need help also
Click to expand...
Click to collapse
have you tried pulling out the battery already?
xlxl said:
same here, i have the MIUI ROM, will try with another version.
Click to expand...
Click to collapse
As I have stated before: Rom change haven't helped me.. Did it work for you ???
Dabarr said:
As I have stated before: Rom change haven't helped me.. Did it work for you ???
Click to expand...
Click to collapse
If changing the ROM didn't help then it is an app issue. One of your apps is causing it. Time to look deeper
I have exactly the same issue! Also with the speaker sometimes. Really annoying. If an app is causing it, how can we find out which one? I'm using ARHD 6.1.0, but I've had the issue with older versions of the ROM too (with the same apps installed).
freakshock said:
I have exactly the same issue! Also with the speaker sometimes. Really annoying. If an app is causing it, how can we find out which one? I'm using ARHD 6.1.0, but I've had the issue with older versions of the ROM too (with the same apps installed).
Click to expand...
Click to collapse
Only way to find out is to test them one by one by reinstalling them one at a time