Hi there,
I've got a lovely new HTC Desire HD , its been working fine for about a month, however something really strange is happening with the camera.
When in the defult camera app, the camera focuses nice and clear, pauses for half a second, then the screen goes black with a large phyisical mechanical shutter sound and feeling, then the camera reinitializes, focuses nice and clear... then the loop continues.
This keeps happening, even while trying to take a picture, if I'm not quick, the picture wont capture.
This doesnt seem to be effected by video mode...
Anyone got any ideas?
-Just to clarify, this is not the phone turning off after taking a picture bug. This is one I can't find anyone else mentioning anywhere. The phone is still one, the camera app just goes black and shutter goes clonk every few seconds after focusing.
Hi, this happened to me as well. I isolated the problem with the OC module I'm using. I don't use the Buzz kernel rather go the GScript route and load the module first, then cpoc then noreboot, oshitt then 100-1459 etc... which I have to do everytime I reboot.
I've tested it quite a few times and the phone sometimes hangs when loading the oshitt script. To remedy the situation, whenever the phone just rebooted, I go to the camera app first, test the video for a few seconds then exit out of the program before loading the GScripts...
Not sure if you are using SetCPU and loading scripts but its as close as I could describe to help you out mate!
Thanks for the reply,
I haven't actually changed anything on this phone from stock, its not rooted nor does it have any form of OC or different ROM to the Orange, thats whats so puzzling.
The phone doesnt restart, just the app. I've narrowed it down to notice this ONLY happens when the camera focuses into something, either by tap or autofocus...
In the interim I've installed camera 360 that seems to work ok, which leads me to believe its more of a software problem then a hardware.
Camcorder started working normally but still no luck with the stock camera app
Maybe when 2.3 is released on dhd, this may resolve?
Sent from my Desire HD using XDA App
Are you running a task killer?
No task killer running, I used to have one bit realised they were not worth the effort, especially after the usb debugging fix!
Sent from my Desire HD using XDA App
I ask because I was having the same issue, and thought it may have been due to the task killer I was using. I think I've found my problem now though... I was using Tasker to control my display brightness, and strangely this caused the camera to exhibit the behaviour you describe. I've modified my Tasker settings to set brightness to Auto when camera is on and this appears to have resolved the problem. So do you have any 3rd party app controlling your screen brightness...?
Sent from my Desire HD using XDA App
Thanks for the reply, I've tried playing around, still no luck, I don't think I have any programs that control the brightness. still can't find many other people who have had this issue. If it carries on, I may try to hard reset as I also can't use Google goggles anymore.
Sent from my Desire HD using XDA App
Hey everyone, I recently updated to KitKat on my phone, and I have noticed a strange issue.
When loading up the camera, whether in the default camera app or on a program such as snapchat, the following thing happens:
The menu buttons and the camera shutter button all appear as normal...
BUT the screen (the camera viewfinder) remains black, and everything freezes for a few seconds. Then the screen shows up the cameras image and everything starts to work as it should.
So it seems like the apps are asking for the camera, but the camera is taking a few seconds to actually boot up. Which is weird, right?
I'm not on a stock ROM, im on the RomAur 3.0 one, but as far as I can tell it is using the standard camera app, and noone else has had this problem. I cam from the previous version of RomAur and the camera in that didnt have any issues either.
Just wondering if this is some glitch or something is interfering? Any suggestions?
Thanks
Try to clean (wipe) all cache.
Send from my Z1C using tapatalk
Had the same issue...
I did a reboot and the problem didn't happen again....
strangely enough this worked, even though clearing the cache and reboots were all things I did since I installed the ROM anyway...
I must have done something in the interim. Silly of me. Seems to be working now anyway so thanks guys
Hello guys,
I have the same problem, I did a factory reset which solved it.
But after some days it appears again, sometime it's working sometime not, it seems to be random...
raphoun said:
Hello guys,
I have the same problem, I did a factory reset which solved it.
But after some days it appears again, sometime it's working sometime not, it seems to be random...
Click to expand...
Click to collapse
Can confirm this.
Sometimes the camera app is working fine and sometimes it takes several seconds to start and it is laggy... :-/
If it lags, but starts okay, rebooting does fix it. No idea what causes it, but it's only done it twice so far.
The far bigger problem is trying to start the camera when it was locked, when there's every chance the camera will freeze and not take or save your picture.
Unlock first then start the camera and all should be fine.
nirurin said:
Hey everyone, I recently updated to KitKat on my phone, and I have noticed a strange issue.
When loading up the camera, whether in the default camera app or on a program such as snapchat, the following thing happens:
The menu buttons and the camera shutter button all appear as normal...
BUT the screen (the camera viewfinder) remains black, and everything freezes for a few seconds. Then the screen shows up the cameras image and everything starts to work as it should.
So it seems like the apps are asking for the camera, but the camera is taking a few seconds to actually boot up. Which is weird, right?
I'm not on a stock ROM, im on the RomAur 3.0 one, but as far as I can tell it is using the standard camera app, and noone else has had this problem. I cam from the previous version of RomAur and the camera in that didnt have any issues either.
Just wondering if this is some glitch or something is interfering? Any suggestions?
Thanks
Click to expand...
Click to collapse
Mine did this as well as other issues. A factory reset did not help but the thing that cured is was a "Repair" from Sony PC Companion. This will perform a factory reset and reflash the OS. Worked for me.
Resets, wipes or repairs won't fix it forever. In fact, I think it's something else that causes problems with the camera app and not the app itself. It's how you start the camera and what was going on at the time that matters.
jonmorris said:
Resets, wipes or repairs won't fix it forever. In fact, I think it's something else that causes problems with the camera app and not the app itself. It's how you start the camera and what was going on at the time that matters.
Click to expand...
Click to collapse
This turns out to be right. After a day or so of no issues with the camera, I tried loading up instagram today and the camera took a long time to load up.
I also notice that even when the camera is loaded, if you try switching to the front-facing camera - that takes a long time to load up too. And same again if you try and switch back to the rear camera.
If this is standard on all kitkat roms for the Z1c then there is some major glitch in there somewhere.
So far it happens on standard app, instagram, and snapchat for sure.
nirurin said:
This turns out to be right. After a day or so of no issues with the camera, I tried loading up instagram today and the camera took a long time to load up.
I also notice that even when the camera is loaded, if you try switching to the front-facing camera - that takes a long time to load up too. And same again if you try and switch back to the rear camera.
If this is standard on all kitkat roms for the Z1c then there is some major glitch in there somewhere.
So far it happens on standard app, instagram, and snapchat for sure.
Click to expand...
Click to collapse
Resurrecting my own thread, as I never actually noticed a fix for this to come up anywhere? I know im not the only one experiencing this, is everyone just living with it?
Its not a huge bother as when it crops up I can do a restart to fix it for another day, but if/when it crops up when im trying to do something quickly its pretty annoying.
I noticed this. Turn off location and it fires right up. That GPS lock can take a few seconds... especially if you're indoors!
charlatan01 said:
I noticed this. Turn off location and it fires right up. That GPS lock can take a few seconds... especially if you're indoors!
Click to expand...
Click to collapse
I always have location turned off, at least the location toggle is turned off. Unless the camera is still attempting to use gps even when the service is deactivated? But then thats still a fault
nirurin said:
I always have location turned off, at least the location toggle is turned off. Unless the camera is still attempting to use gps even when the service is deactivated? But then thats still a fault
Click to expand...
Click to collapse
Hmm, that's how I disable it... and I haven't noticed the lag. I should say, I am currently running a CM based ROM - PA.
charlatan01 said:
Hmm, that's how I disable it... and I haven't noticed the lag. I should say, I am currently running a CM based ROM - PA.
Click to expand...
Click to collapse
Oh well then its unlikely to be the same problem, as CM (as far as I know) doesnt use the same camera/framework/etc as the stock sony.
I have the same lag on my Z1C (CM Nightly), but it only occurs the first time I start the camera after a reboot. I just start the camera once I have rebooted the phone (you can kill it via task manager again and it still works!) and do not have any lags afterwards that could prevent a quick shot. It's not perfect, but it works.
Same here with cm 11.
Nash123 said:
Same here with cm 11.
Click to expand...
Click to collapse
Then its a completely different problem, cos on the stock android after a reboot the camera is fast straight away, and its only after an indeterminate amount of time (hours/days) of running that the camera will then become slow to load. And then a restart fixes the problem.
Clearly CM uses a different camera, or some other different piece of coding, that isnt the same in the stock sony build.
I installed port camera from z2 and i dont have lags. On stock camera i had couple of lags and crashes but for now with new camera is good
Wysłane z mojego D5503 przy użyciu Tapatalka
mosespl said:
I installed port camera from z2 and i dont have lags. On stock camera i had couple of lags and crashes but for now with new camera is good
Wysłane z mojego D5503 przy użyciu Tapatalka
Click to expand...
Click to collapse
Does the ported Z2 camera overwrite the Z1 camera? As in, will apps like snapchat etc use the Z2 camera code instead of the Z1 code?
Because the problem isnt just with the default camera app, its with every app that uses the camera. Snapchat, instagram, facebook, whenever you load up the camera on any of them, theres a 5 second delay while the camera screen stays black, until the camera then switches on and starts working.
BUT not all the time, after a fresh reboot they all work instantly like they should. Its only after a few hours or whatever that the camera starts misbehaving. Something is causing interference.
After more than 1.5 yrs of using my Note 2, recently I noticed that sometimes the camera focus gets stuck. It seems to be at macro focus distance. So everything close to the lens will be clear, and things beyond that blurred. There is no way to refocus. No matter what I do (using manual touch focus, setting to autofocus, setting to macro focus, setting to video mode, killing the camera app or restarting the phone) it is stuck for some time. And then it just starts to work again by itself after few minutes. Completely randomly it seems. I'd say it gets stuck approx every 5th time when I turn the camera on.
If I look at the lens, while the focus is stuck, the lens, naturally, also don't move as they move when the focus is not stuck.
What could this be? My bet would be an issue with camera, but I'd like to exclude any possible known issue, before I RMA it. I still have few months of warranty. Normally I would be doing the factory reset, but I was kinda waiting for the 4.3 or 4.4.2 update, and fresh flash.
I'm running stock 4.1.2 (still the latest official for me), and it is rooted, and triangled away. Everything else is stock. I use stock camera app. Also I don't seem to have any other problems. When it does focus, the camera produces sharp photos. SO no problems there either.
PS The lens are clean and undamaged, as is the whole phone.
bump
Many people say they never had a camera issue on Android N but I'm still suffering from that.
Nothing more, just like the old days: When I try to activate the camera app, the whole phone will freeze and reboot in a few seconds. After that, I still cannot use camera unless I reboot my phone again because camera app always FC or says "can't connect to camera".
Is there anybody dealing with the same problem? I'm not sure if it's a hardware issue because when it is fine, it works fine, I can take any photo for a period and after a while it broken again.
Tried flash any ROMs like factory image, xTraSmooth, Stock+, Bliss and CM, they doesn't fixed anything. Even if there are no 3rd party apps in my phone, this issue still happens.
I have a different problem
My problem is with the HDR+ function. Yellow to brown vertical stripes appear on the photo whenever I snap a pic of a white object or white background. It only happens when I shoot something white with HDR+ on. Anybody else has this problem?
https://code.google.com/p/android/issues/detail?id=201248
Sent from my Nexus 5X using XDA-Developers mobile app