Database Develop

Occasional reboot after camera use

Has anyone else experienced a reboot after camera use? It doesn't happen all the time for me, but it's regular enough that I'm pretty certain that I can pin it to my camera. I'll take the phone out of my pocket, take a photo, quit out of the camera app, and when I pull my phone out of my pocket later, it's either off or it's rebooted itself. The battery is fine when it restarts, and it doesn't seem to happen immediately. This also seems to happen no matter how I activate the camera or how/whether I quit the app or return to the home screen when I'm done. If my GSam graph is accurate, it doesn't look like it's linked to high temperature, either. Has anyone else experienced this, or does anyone have any ideas?
I'm on a t-mobile Moto X, btw, unrooted and running Nova launcher on 4.4.2.

Never heard of this issue on the x. If you wanna get drastic try a factory reset or at least clearing the data for your camera app.
Could contact about a replacement too.
Sent from my DE Moto X

Using Motorola Camera can cause background apps to close

It seems like there's a 50% chance that when I take a photo with the Motorola camera, it causes Screen Balance (and often Tasker) to close. They'll restart themselves after a period of course but I'm curious as to whether anyone has experienced this themselves.

Not only that, I get major redraws on the home screen.

Yeah, it's like Motorola Camera suddenly eats all the RAM for a second, kicking everything else out of memory (hence the launcher redraw). I don't get why though. So long as it isn't just me being crazy.

I just got my XT1095 last night and had this issue in the morning. Glad I'm not going crazy. BeyondPod and Waze shut off on me when I took a photo while driving to work. I'm on 22.21.11 so it's definitely there in the latest version.
Where does one report bugs for Motorola apps?

I face the same problem: using camera kills Google Maps navigation.

Test: I got waze and Google nav running at the same time, opened some random apps and then opened Camera. Took a pic, a video. Waze and Google nav still running. I'm still on kit kat
Are you all on lollipop?

CUBENSIS said:
Are you all on lollipop?
Click to expand...
Click to collapse
Not me, I'm on AT&T so stuck on KitKat.

hyperspacey said:
Yeah, it's like Motorola Camera suddenly eats all the RAM for a second, kicking everything else out of memory (hence the launcher redraw). I don't get why though. So long as it isn't just me being crazy.
Click to expand...
Click to collapse
I have a little bit different issue. I noticed that I can do the twist launching, so I open the camera manually, and have the same issues like you guys. I'm not sure about whether this is the camera problem or the other services that linked to the camera.
Thanks to you guys. I will avoid using moto camera for a while, although it works fine so far.

I'm on KK. The annoying thing is it isn't 100% reproducible. I sent Motorola an email via the Play Store listing for the Camera app, if anyone else feels like doing it too go ahead. https://play.google.com/store/apps/details?id=com.motorola.camera

Flashlight/Camera Bug Back in 5.1

Remember the bug a while back where if you turned on the flash, it would time out in a minute or so and turn itself off? And then you would get the "Cannot connect to camera" bug and couldn't use the flash or camera until you rebooted?
That was either in the L dev preview or 5.0.0, i don't remember. It seemed to be fixed in the latest patch prior to 5.1, though.
Sadly, it appears to be back in 5.1. Is there an open bug for this?

Oh gawd

lotherius said:
Remember the bug a while back where if you turned on the flash, it would time out in a minute or so and turn itself off? And then you would get the "Cannot connect to camera" bug and couldn't use the flash or camera until you rebooted?
Click to expand...
Click to collapse
FWIW, I have never been able to duplicate the problem on my N5, either with 5.0.1 or with 5.1. Just now I turned on the flashlight via the quick settings shade and left it on for over 10 minutes. It stayed on all that time, and after I turned it off, the camera is working fine. I don't know what to conclude, but I'm glad I'm not experiencing the problem.

Also was there with 5.0.1
Sometimes the flashlight worked, but most of the time it behaved the way as in OPs post.
Annoying, especially since Xposed also doesn't work with 5.1.....used the Wanam Torch module the whole time.

Yeah Wow and I thought I was the only person with this problem I thought my flashlight LED blew out the first time it happened because it wouldn't turn back on until after I Rebooted.

yup, had the problem just now..

The bug is NOT because of Android.
The bug is that one of your APPS is poorly written, it is using the camera HAL and is not releasing it properly after use, as only one process can use the camera HAL at any given time.
Such culprit apps are usually video call apps (e.g. Skype), instant photo-sharing apps (e.g. Snapchat), flashlight apps, or a poorly written 3rd party camera app.
The timing out is likely to prevent you from burning out the flash, as it's main purpose only involves a brief flash, not continuous use.

Elluel said:
The bug is NOT because of Android.
The bug is that one of your APPS is poorly written, it is using the camera HAL and is not releasing it properly after use, as only one process can use the camera HAL at any given time.
Such culprit apps are usually video call apps (e.g. Skype), instant photo-sharing apps (e.g. Snapchat), flashlight apps, or a poorly written 3rd party camera app.
The timing out is likely to prevent you from burning out the flash, as it's main purpose only involves a brief flash, not continuous use.
Click to expand...
Click to collapse
Wrong, faced it on Day 1 when i was in 5.0, it was a clean flash of factory image with no user apps installed.
In 5.1 so far i haven't encountered that bug.

Didnt experience it before 5.1 but now do

It did it on the developer preview also
Sent via tapatalk from my cataclysm'd Lollipooop Nexus 5

I had this bug from 4.4 and still happening, im used to it not a big deal. Just dont keep flash on longer then 10 min.

Elluel said:
The bug is NOT because of Android.
The bug is that one of your APPS is poorly written, it is using the camera HAL and is not releasing it properly after use, as only one process can use the camera HAL at any given time.
Such culprit apps are usually video call apps (e.g. Skype), instant photo-sharing apps (e.g. Snapchat), flashlight apps, or a poorly written 3rd party camera app.
The timing out is likely to prevent you from burning out the flash, as it's main purpose only involves a brief flash, not continuous use.
Click to expand...
Click to collapse
Not using any of those things you mentioned.
And what you call a prevention from burning out the flash....I don't know man, since when did "having to reboot your phone because the flash would never turn back on after it turned off by itself" become a feature?

Elluel said:
The bug is NOT because of Android.
The bug is that one of your APPS is poorly written, it is using the camera HAL and is not releasing it properly after use, as only one process can use the camera HAL at any given time.
Such culprit apps are usually video call apps (e.g. Skype), instant photo-sharing apps (e.g. Snapchat), flashlight apps, or a poorly written 3rd party camera app.
The timing out is likely to prevent you from burning out the flash, as it's main purpose only involves a brief flash, not continuous use.
Click to expand...
Click to collapse
So you're telling me.. When I drop down the notification page and toggle "Flashlight" and it goes out it's the "APPS" Fault. Which is the built in notification area?

I've never had a problem regarding this, fortunately.

https://code.google.com/p/android/issues/detail?id=79565
Everyone comment and star the issue

markdapimp said:
https://code.google.com/p/android/issues/detail?id=79565
Everyone comment and star the issue
Click to expand...
Click to collapse
Don't comment unless you have useful input for the developers - commenting just spams everyone on the list, meaning many will un-star it. Just star it instead.

Have this bug on clean install of 5.1
Pretty random in nature

I had the same issue and I solved going in the development option and I switched on the Awesome player option.
Seems it works. I had for 2 minutes the flash light on without problems

Initially I didn't think I had it....and I don't on a fresh boot when no notifications come in. Then I had the flashlight on and an e-mail (Gmail) notification came in, and I couldn't turn off the flashlight. Before 5.1 had it stuck on every time if the screen timed out, at least that is fixed (I think).

coluichepensa said:
I had the same issue and I solved going in the development option and I switched on the Awesome player option.
Seems it works. I had for 2 minutes the flash light on without problems
Click to expand...
Click to collapse
I have no idea why this worked, but it did. 10+ minutes, no timeout!
this has been the most infuriating bug I have experienced going all the way back to making my htc ozone run on gingerbread.
has been present on every variation of lollipop I could find. my flash light would time out in 2 minutes or so.
Thank you so much!

Phone shutsdown when Location enabled

Hi all,
I'm running out of ideas and could use another opinion please:
N6 running 5.0.2 (this is the second one incidentally, I sent the first one back for this same problem) - the phone will shutdown under certain circumstances. When this happens it does not restart, you have to press the power button to restart it. Mostly this happens when I use the Google Camera stock application to take a photo but only ever when the phone is not connected to WiFi. I have had it happen when I open the camera app as well (without taking a picture), if you put your ear to the upper speaker as soon as the camera app is opened you can here a cell location signal (similar to the sound you hear when you put your phone near a speaker) and then the phone turns off. I can stop this happening by using a third party camera app. I can also stop this happening if I disable Google location.
Yesterday I wiped the phone, signed in with my Gmail, and took 25 pictures, all OK. I then turned on Google Now, took one photo and the phone turned off. This is definitely something to do with location data but I don't understand why nobody else is experiencing this ? Maybe the phone is faulty but I'm going to have a hard to explaining that as I sent the last one back for the same reason.
Any suggestions are greatly appreciated.
Thanks,
Simon.

Glad I'm not the only one having this issue. I've seen this happen on my N6 too, both on 5.0.x as well as on 5.1. I've seen this happen even while unlocking the phone (I have face unlock enabled), and yes this happens mostly when using the camera. Never knew it has to do something with location services.
I'm running completely stock and unrooted by the way. I guess I should try flashing the factory image

Yes same with me, stock phone unrooted and although using the camera is the best way to get this to happen you are right, it sometimes happens at other times as well. If I go to an area with no WiFi and poor phone signal I can get it to happen everytime the Google Camera app is opened, so I have to resort to taking pictures in Airplane mode.
This has happened to me since I have had this phone and its replacement and I am curious to know why, when you open the Google camera app, if you immediately put your ear to the upper speaker it becomes active for about 3 seconds ? After that three second burst of sound the phone will turn off. To me, it sounds like a location signal is being sent when the camera is opened.

Yet turning off geolocation?
Sent from my Nexus 6 using Xparent Skyblue Tapatalk 2

same thing happening here,i was out today and when i tried to open the camera app phone kept crashing,soon as i was home on wifi camera app worked fine,i've switched off the location thing to see if that helps

"Can't connect to camera" - Nexus 6 error with Lollipop 5.1

My Nexus 6 is unable to start the camera. The google camera app hangs when it starts and nothing shows up. Earlier the camera used to open but it lagged a bit when HDR was on. Now the camera isn't opening anymore. The other apps like Instagram that use the camera are also not able to open it. The app opens up and hangs, nothing shows up just black screen and sometimes the message "Can't connect to Camera" appears. This issue came after 5.1 and I also had buzz launcher installed once but then I removed it. The phone is less than 7 months old and I bought it online from Flipkart (Indian e-commerce site).
What I've tried:
Forced stop the app (Google Camera)
Cleared cache of the app
Booted in recovery mode and wiped cache partition
Factory reset the device
Nothing worked for me, I tried these steps one by one and then tested the camera but it is still not working. Please help me with this, I paid a lot of money for this phone on my own and it feels really bad and annoying that the camera isn't functional anymore.
Thanks in advance.

roboy1000 said:
Nothing worked for me, I tried these steps one by one and then tested the camera but it is still not working.
Click to expand...
Click to collapse
You could try a different camera app.
Camera FV-5.

Camera is a nightmare
Here's my issue with the camera:
I've been on lollipop for a while and I haven't had a problem with it, until the camera decided to take a vacation on me. When it comes to taking pictures, the phone crashes and an icon shows my battery is dead, this happens on a full to half life, so I'm not sure what it's trying to pull here. I've cleared and cleaned the phone, my last option is to reset, though I have a feeling this won't work, since I'll still need the latest android update, so I'm back to square one.
The latest issue Is when it comes to uploading pictures, the phone crashes with the same error sequence.
And the finally issue is the sound the device makes sometimes with the camera. Which is curious because I am careful but it looks like I'm having issues from different sources. I'd like to rule out the software side first.
For the time being, I've disabled the camera completely.

nothman said:
Here's my issue with the camera:
I've been on lollipop for a while and I haven't had a problem with it, until the camera decided to take a vacation on me. When it comes to taking pictures, the phone crashes and an icon shows my battery is dead, this happens on a full to half life, so I'm not sure what it's trying to pull here. I've cleared and cleaned the phone, my last option is to reset, though I have a feeling this won't work, since I'll still need the latest android update, so I'm back to square one.
The latest issue Is when it comes to uploading pictures, the phone crashes with the same error sequence.
And the finally issue is the sound the device makes sometimes with the camera. Which is curious because I am careful but it looks like I'm having issues from different sources. I'd like to rule out the software side first.
For the time being, I've disabled the camera completely.
Click to expand...
Click to collapse
update to android version 5.1.1?

roboy1000 said:
My Nexus 6 is unable to start the camera. The google camera app hangs when it starts and nothing shows up. Earlier the camera used to open but it lagged a bit when HDR was on. Now the camera isn't opening anymore. The other apps like Instagram that use the camera are also not able to open it. The app opens up and hangs, nothing shows up just black screen and sometimes the message "Can't connect to Camera" appears. This issue came after 5.1 and I also had buzz launcher installed once but then I removed it. The phone is less than 7 months old and I bought it online from Flipkart (Indian e-commerce site).
What I've tried:
Forced stop the app (Google Camera)
Cleared cache of the app
Booted in recovery mode and wiped cache partition
Factory reset the device
Nothing worked for me, I tried these steps one by one and then tested the camera but it is still not working. Please help me with this, I paid a lot of money for this phone on my own and it feels really bad and annoying that the camera isn't functional anymore.
Thanks in advance.
Click to expand...
Click to collapse
From the Google product forums it looks like a failure of the camera app to close properly after use.
https://productforums.google.com/forum/m/#!category-topic/nexus/using-the-camera/aY0X1QiGuhY
Either by use of a 3rd party app that uses the camera or the flashlight. Also it seems that using face unlock can cause the issue.
That being said, and you've reset the device... Have you tried the camera right after the reset (without 3rd party apps)?

shel692 said:
From the Google product forums it looks like a failure of the camera app to close properly after use.
Either by use of a 3rd party app that uses the camera or the flashlight. Also it seems that using face unlock can cause the issue.
That being said, and you've reset the device... Have you tried the camera right after the reset (without 3rd party apps)?
Click to expand...
Click to collapse
Yes, I tried the camera just after the reset and it did not work. I think the OS should be responsible to handle the apps and how are they being closed. Google is not working upto the mark on this. I still need help

roboy1000 said:
Yes, I tried the camera just after the reset and it did not work. I think the OS should be responsible to handle the apps and how are they being closed. Google is not working upto the mark on this. I still need help
Click to expand...
Click to collapse
Sadly, it seems like you have 2 options, sucking it up and installing another camera or RMA the device.
I wish that wasn't the case for you, I'm disappointed too. I love this phone.
"Do not meddle with cats for they are subtle and will*piss on your keyboard"