My wife and I both have the Nexus 5. I'm still on KitKat while she is on lollipop. She is completely stock and upgraded to lollipop via ota. I tried to take pictures in low light so I set the flash to always on. I noticed sometimes it would not flash, sometimes it would flash, and sometimes the flash would come on and stay on leaving the app in a hung state. Anyone else? Or should I just consider a different app from the Play Store?
Not an issue for me stock 5.0. I flashed factory image didn't wait for OTA. Try clearing cache and data on camera app?
Jnewell05 said:
Not an issue for me stock 5.0. I flashed factory image didn't wait for OTA. Try clearing cache and data on camera app?
Click to expand...
Click to collapse
I thought of clearing the cache after I posted this, so I did. Now it seems the flash doesn't work at all even when set to be on all the time. I guess I will just stick to HDR on her phone
I've got problems too, and I looked for it in the web. Seems to be a known bug, when you use the torch then the camera has problems and crashes sometimes too.
Anyway rebooting fixes everything. Apparently here in xda nobody has started investigating this
Sent from my Nexus 5 using XDA Free mobile app
Daemo00 said:
I've got problems too, and I looked for it in the web. Seems to be a known bug, when you use the torch then the camera has problems and crashes sometimes too.
Anyway rebooting fixes everything. Apparently here in xda nobody has started investigating this
Sent from my Nexus 5 using XDA Free mobile app
Click to expand...
Click to collapse
I'm wondering if using a third party led flashlight app (tiny LED is good) would resolve if it's just a Google issue? I cant we why it's a camera issue, I'm putting my money on the Google flashlight code.
Related
Hi guys, I'm having issues with the video recorder on my NS. Whenever I try to record video clips the picture and sound slip out of sync, the image freezes, leaving the sound running. The video then continues but is behind the sound.
I can't find any suggestions about how to fix this. Does anyone here have any idea?
I just took some footage of 3 mins to test it again and actually the picture freezes near the end of the video. After that the audio is out of sync. I'm on infin1tyROM 1.1.0. :S
Sent from my Nexus S using Tapatalk
I have the same ROM installed, I mentioned the issue in the thread but someone else has said they don't have the issue, I wonder if it only affects longer clips or if there's something about the way we installed the ROM perhaps?
Well actually it was me stating that it works fine, but now i had to correct it. You got a i9023 or i9020?
I have the 4g and last night I was recording 10 minute segments and didn't see anything wrong. I would heavily suspect if a CPU hog app decided to do something while recording video, that it could cause problems. Out of an hour of recording, I think I might have seen a time when something caused the screen to black out for a second and start a new recording. Maybe.
I9020 here
Sent from my Nexus S using XDA App
Well if you found a solution please let me know! I*tried uninstalling some apps, several reboots, dalvik cache wipe, permission fix, different video players, no luck. Maybe it's the UV kernel? I*fear that I*had the same problem on CM7 with stock kernel but I'm not sure...
I'm stock rooted. That's it
Well as soon as I*have time I'll flash back to CM7 with stock kernel and report back.
@tatwamasi could you please test something for me? maybe this fixes the problem: reboot into recovery, wipe dalvik cache then reboot and go to settings, applications, camera and clear data. take 5 mins of video to see if it worked.
Sent from my Nexus S using Tapatalk
Here's a thought. If you transfer the videos to the computer and play them there, do they skip on the pc?
TubeShaped said:
@tatwamasi could you please test something for me? maybe this fixes the problem: reboot into recovery, wipe dalvik cache then reboot and go to settings, applications, camera and clear data. take 5 mins of video to see if it worked.
Sent from my Nexus S using Tapatalk
Click to expand...
Click to collapse
Cheers for the suggestion I'll try that later and report back. Earlier I made a Nandroid backup, did a full wipe, reinstalled the Rom and tested the camera. Video seemed fine then the camera started FC'ing. Not sure what's going on there... I've never had that before. Weird. Back on The backup now.
@herbthehammer I*feel stupid for not having tried that already :S
@tatwamasi have you tried fixing permissions in CWM?
After some testing I can confirm that clearing the camera app data actually solves the problem.
Lol sry for all the * after "I" my desktop keyboard is acting weird.
Having this exact problem on a Sprint NS4G. It has a CM7 nightly installed. Will try clearing the data on the camera app. Hoping that fixes it!
Hey guys
I'm having a problem with the camera of my moto g. Everytime I open the camera and shut it down, but then open it again, it isnt working anymore. There's a black screen with a popup saying 'Camera error: camera cannot initialize'
I can hear the camera 'cracking' when its launching our shutting down. When I wait 4 seconds till it is shut down it works again but otherwise not. When I install stock rom from scratch problem is gone, but now I rooted (stock kitkat) with faux kernel OC and the problem came back!
Are there other people experiencing the same problem? Is there a fix possible?
Thanks in advance
Go app>all>camera>clear data and cache> force stop then reboot device
Sent from my XT1034 using xda app-developers app
I had the same issue. Did all suggested in various forums on cache and all.
What worked for me is that I installed a 3rd party app, Camera Zoom Fx. This works fine but additionally the in-built camera app also started working fine. Its been a couple of days now.
Hi Guys,
It seems that Skype is locking the camera. Remove app cache and data, remove app and reboot the phone.
Cheers
guidonno said:
Hi Guys,
It seems that Skype is locking the camera. Remove app cache and data, remove app and reboot the phone.
Cheers
Click to expand...
Click to collapse
I also experienced the same problem. via instagram, I also can't connect to camera. I dont know if it had been due to Skype, but I downloaded it a couple of days ago, but I also switched to ART so I really don't know what caused it. now I'm back to dalvik and what I did was I removed app cache and data and then rebooted the phone. PROBLEM SOLVED, with Skype still installed..
I got my moto g 4 days back and the camera was working fine, all of a sudden it stopped working and i getting the same error camera cannot camera cannot initialize.
I have tried everything soft reset, hard reset, rebot, cache partitioning format, clear data, still the problem persist.
Please Advice.
Thanks in advance
Anyone noticed how when you press the back button to exit and application too fast, the screen for you recent apps also display before you are taken back to the home screen?
This issues started after 4.4.3
Anybody have any solutions?
It's always been a weird KitKat bug, for me it brings up a random app from somewhere in the recents list that's not even been used for a while. Lol
Sent from my Nexus 5 using Tapatalk
dogstar55 said:
Anyone noticed how when you press the back button to exit and application too fast, the screen for you recent apps also display before you are taken back to the home screen?
This issues started after 4.4.3
Anybody have any solutions?
Click to expand...
Click to collapse
Yes, not a 4.4.3 specific issue sadly. Was hoping this would have been resolved in the latest update but clearly not. D'oh. I'm completely stock everything, unrooted and it's happened since I bought the phone in February.
Ref: http://forum.xda-developers.com/google-nexus-5/help/random-app-pops-button-exit-t2680148
I am completely stock too. I only started noticing it since 4.4.3 - or maybe it was always there.
Its quite irritating. Is google looking at this?
I've seen a dramatic increase since 4.3.3. Doesn't do it all the time but once it starts it seems to keep doing it for a while.
I cleared Cache and Dalvik but didn't make any difference.
Think this happened to me once recently, opened Google Chrome on its own.
Maybe it's not a bug. Returning to a previously used app could be seen as a convenience. Just a thought.
Sent from my Nexus 5
I've never experienced this issue. Why not just press the home button to exit the app?
georgios73 said:
Maybe it's not a bug. Returning to a previously used app could be seen as a convenience. Just a thought.
Sent from my Nexus 5
Click to expand...
Click to collapse
Lol. No it returns to any random app ib the recents list, not the last opened
Sent from my Nexus 5 using Tapatalk
I can confirm this starting from 4.4.3. It's quite simple to reproduce it for me:
Open Chrome and press the home button.
Open WhatsApp and enter a conversation. Press the back button two times quickly.
This should bring you back to your home screen. Instead it immediately will pop up Chrome for a moment, just to close it automatically afterwards. I press the back button two times in a lot of apps, so this is starting to be really annoying. I'm running everything stock. Has anyone experiencing the issue tried to hard-reset the phone to see if it goes away?
I used to face this on stock rom as well... Ever since I've started using a custom rom (AICP) , the bug has disappeared.
- Sent from an IceCold Hammerhead!
dogstar55 said:
I am completely stock too. I only started noticing it since 4.4.3 - or maybe it was always there.
Its quite irritating. Is google looking at this?
Click to expand...
Click to collapse
I can confirm it only started coming up since 4.4.3. It did not happen on 4.4.2.
I'm using stock Nexus 5, with Nova launcher.
jpabloae said:
Has anyone experiencing the issue tried to hard-reset the phone to see if it goes away?
Click to expand...
Click to collapse
I've tested it myself and I can confirm that a factory reset does not solve this issue.
Confirm, but true only for stock 4.4.3. Fast pressing back button to exit an app will cause opening last active app (f.e. open dialer with messaging app in background, twice-triple tap back and it will close dialer but bring messaging app right from home screen and close it (wut?)). Running custom and there is no such bug.
arshum said:
I can confirm it only started coming up since 4.4.3. It did not happen on 4.4.2.
I'm using stock Nexus 5, with Nova launcher.
Click to expand...
Click to collapse
it was there in 4.4.2 as well.
I have been facing this issue since I bought it.
Sent from my Nexus 5 using XDA Free mobile app
Z3US911 said:
it was there in 4.4.2 as well.
I have been facing this issue since I bought it.
Sent from my Nexus 5 using XDA Free mobile app
Click to expand...
Click to collapse
Ditto
After applying the 4.4.4 OTA this bug still seems to be present.
Hey,
The camera for me keeps force closing when I try to open it :crying:. A reboot fixes it temporarily, but it reverts back after a while. It also prevents me using any app where the camera is used.
Has anyone else had this problem? Any way to fix it?
Thanks
You don't happen to be under volted
Nope! I havent changed any settings on the phone. Its getting quite irritating
Having the same problems with my nexus 5 on lollipop. " Can't Connect to Camera" keeps popping up. I've tried rebooting, clearing cache and data, but to no avail.. Any fix?
Do you use the torch?
Sent from my Android 5.0 Nexus 5
I have sued it once as far as I remember. Have many others been having this problem?
Everytime when I turn off my screen while listening with headphones on or off, my music disrupts after a period of 6 seconds.
Now I have tried a various things to fix it, and strangely enough disabling the lock screen (any type of security ) fixes this issue)
Might any of you know a better alternative to make my life easier? I don't want to leave my phone insecured for the sake of listening to music.
Thank you.
Sent from my SM-G920F using XDA Free mobile app
Reflash with stock 5.1.1 ROM via odin.
Have you (TS) tried the solution provided above? I'm experiencing the bug as well. It's really irritating.
I managed to fix the problem by clearing the system cache. Just boot into odin, clear the cache and restart the phone.
(I didn't reflash the stock rom)
Sent from my SM-G920F using XDA Free mobile app
Thanks for the reply. When you mean boot into odin, did you mean recovery? I have done that as well, but it seems that it didn't fix the problem for me.
To add another solution to this bug, I downloaded and flashed the stock ROM for my phone. Apparently, it fixed the bug.
Yes that's what I meant, sorry for the confusion. I might as well do the same. Thanks for the heads up !
Sent from my SM-G920F using XDA Free mobile app
Heya, sorry to bring this topic back again to life. Apparently, the fix was only temporary. The bug reappeared after a few hours. I might try a clean install just to see if this gets fixed.
Edit: My device model number is SM-G920F
Makxx said:
Thanks for the reply. When you mean boot into odin, did you mean recovery? I have done that as well, but it seems that it didn't fix the problem for me.
To add another solution to this bug, I downloaded and flashed the stock ROM for my phone. Apparently, it fixed the bug.
Click to expand...
Click to collapse
Do you have greenify installed and have the music app set to greenify? Also are you using the built in close app feature? The one found in battery stats. If so do you have the app set to auto kill? This feature kills all selected apps after a certain time of the screen being turned off.
drock212 said:
Do you have greenify installed and have the music app set to greenify? Also are you using the built in close app feature? The one found in battery stats. If so do you have the app set to auto kill? This feature kills all selected apps after a certain time of the screen being turned off.
Click to expand...
Click to collapse
I haven't installed Greenify yet on my S6. I had it on my S4, but it wasn't causing any problems at all. I checked the close app feature, and Music app wasn't placed there. The Music app crashes, it doesn't just close; without any warning message or whatever.
Update: I did a factory reset/data wipe via recovery mode, and used Odin to install a fresh 5.1.1. I tried the Music app, and it doesn't crash. I hope it wouldn't crash anymore.
Makxx said:
I haven't installed Greenify yet on my S6. I had it on my S4, but it wasn't causing any problems at all. I checked the close app feature, and Music app wasn't placed there. The Music app crashes, it doesn't just close; without any warning message or whatever.
Update: I did a factory reset/data wipe via recovery mode, and used Odin to install a fresh 5.1.1. I tried the Music app, and it doesn't crash. I hope it wouldn't crash anymore.
Click to expand...
Click to collapse
Did the fresh install fixed the problem completely? I have it as well and it's super annoying, it will be super annoying to have to download my apps again but i will if it fixes the problem.
DJ_Jedi said:
Did the fresh install fixed the problem completely? I have it as well and it's super annoying, it will be super annoying to have to download my apps again but i will if it fixes the problem.
Click to expand...
Click to collapse
Unfortunately, it did not. To be exact, it fixed the problem for about a week, but the problem appeared again. Try using Power Amp music player, it's working well for me. I'm tempted to buy the full version after this trail version expires. Spending 1$ would be way better than getting annoyed all the time by the default music player.
Makxx said:
Unfortunately, it did not. To be exact, it fixed the problem for about a week, but the problem appeared again. Try using Power Amp music player, it's working well for me. I'm tempted to buy the full version after this trail version expires. Spending 1$ would be way better than getting annoyed all the time by the default music player.
Click to expand...
Click to collapse
The problems is i use play music because of the cloud feature, let's hope the Edge+ update fixes the problem, otherwise I'm going back to 5.0.2