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
Related
I love the Moto X. Wanted one when it was first announced and I ended up buyiing the VZW DevEd through the Black Friday sale. Lately I have been having a lot of problems with my phone and Im not sure what is going on and if it is an app update or a system problems but I'll describe the issues I am having and will let you guys suggestion ideas of how to fix it.
1) When ever I open up the stock contacts app it is always saying "Contacts list is being updated". Some times I'll open it up and I can see all the contacts listed correctly but when I select a contact to view its details I just get a blank screen.
2) This might be due to the contacts app, but when every I receive a phone call from a known contact the phone app only provides me with the phone number and not exactly who the caller is as defined in the contacts. Also when I receive a phone call while the phone is locked with the screen off the screen does not light up but the ring tone is played. Even picking up the phone does not light up the screen. I have to hit the lock button which silences the phone then hit it again to light the screen up then I can select answer or end call. Thats all hoping the caller is still callling me as this process takes a while.
3) Kind of the samething above but with the stock clock app and an active alarm. The phone has been super laggy that I can't silence or snooze and alarm in the morning quickly. I have to place my finger on the ring wait a few seconds to see it light up that I have selected the ring then I can move it to dismiss or snooze. When I select one of those options and let go it will pause on the screen and stay light for 10 seconds and then the selection will process correctly
4) This may be subjective but I think my battery life right now is really bad. I check the battery stats and it seems fine but when I use it the battery seems to drain really fast.
5) This isn't subjective. Everything is laggy from loading an app to displaying the recently used apps. I've tried uninstalling things, disabling things, enabling things and nothing seems to work. Its especially laggy when going from phone locked screen off to the home screen. It is no where as responsive as it once was. I was even down to 4GB of storage left out of 32GB so I cleared a bunch off the SD card and still its laggy.
So what do you guys think? Should I reset the phone or has someone experienced something similar and knows how to fix it. FYI, I am using Apex Pro as my launcher.
Talguy said:
I love the Moto X. Wanted one when it was first announced and I ended up buyiing the VZW DevEd through the Black Friday sale. Lately I have been having a lot of problems with my phone and Im not sure what is going on and if it is an app update or a system problems but I'll describe the issues I am having and will let you guys suggestion ideas of how to fix it.
1) When ever I open up the stock contacts app it is always saying "Contacts list is being updated". Some times I'll open it up and I can see all the contacts listed correctly but when I select a contact to view its details I just get a blank screen.
2) This might be due to the contacts app, but when every I receive a phone call from a known contact the phone app only provides me with the phone number and not exactly who the caller is as defined in the contacts. Also when I receive a phone call while the phone is locked with the screen off the screen does not light up but the ring tone is played. Even picking up the phone does not light up the screen. I have to hit the lock button which silences the phone then hit it again to light the screen up then I can select answer or end call. Thats all hoping the caller is still callling me as this process takes a while.
3) Kind of the samething above but with the stock clock app and an active alarm. The phone has been super laggy that I can't silence or snooze and alarm in the morning quickly. I have to place my finger on the ring wait a few seconds to see it light up that I have selected the ring then I can move it to dismiss or snooze. When I select one of those options and let go it will pause on the screen and stay light for 10 seconds and then the selection will process correctly
4) This may be subjective but I think my battery life right now is really bad. I check the battery stats and it seems fine but when I use it the battery seems to drain really fast.
5) This isn't subjective. Everything is laggy from loading an app to displaying the recently used apps. I've tried uninstalling things, disabling things, enabling things and nothing seems to work. Its especially laggy when going from phone locked screen off to the home screen. It is no where as responsive as it once was. I was even down to 4GB of storage left out of 32GB so I cleared a bunch off the SD card and still its laggy.
So what do you guys think? Should I reset the phone or has someone experienced something similar and knows how to fix it. FYI, I am using Apex Pro as my launcher.
Click to expand...
Click to collapse
Try resetting your phone, if that doesn't work, then talk to motorola support. This stuff shouldn't happen and I'm sure Motorola's support team will be happy to help you.
danny39 said:
Try resetting your phone, if that doesn't work, then talk to motorola support. This stuff shouldn't happen and I'm sure Motorola's support team will be happy to help you.
Click to expand...
Click to collapse
So I think I fixed the problem last night with out resetting the phone based on something I mentioned here. I stated that I'm using Apex as my launcher. Not sure why I didn't think of this before, but last night I decided to change back to the stock launcher and closed out of apex in the recent apps menu. Everything got super snappy when going from view to view and launching apps. I then loaded Apex back up and it all seemed to work just fine. This morning when my alarms went off I didn't experience the problem that I was describing about above.
So I'm going to consider this issue fixed, however I will keep an eye on it to see if it comes back.
The other day I switched my runtime to ART from Dalvik, which I much prefer. Everything was running fine until I picked up my phone and realized that the Active Display didn't come to life. Then the power button wouldn't make the phone respond (battery was at 75%) either. So I did a 3-button reset of the phone.
After the phone boots up I go to the home screen, then all of a sudden the screen stops responding to my touch and the screen fades to black. Again, Active Display doesn't appear and the power button doesn't wake the screen up. Holding the power button down by itself does nothing... only a 3-button reset will reboot the phone. This continues for an hour or so until my phone finally stays awake and stops misbehaving.
The following day my phone seems fine. Played a couple games, used Maps to navigate, and a half dozen other apps for an hour or two. Then after taking my phone out of my pocket a little later, there's no Active Display and the power button doesn't work. [emoji35]
The only app I have had any problems with is Hangouts... where the app would randomly force close. Thinking this might be the culprit, i uninstalled the updates for Hangouts and took it back to it's stock state (since I can't uninstall it outright). But alas, the issue happens maybe twice more, seemingly at random throughout the rest of the day.
This morning I switched back to Dalvik and have yet to have a weird shutdown. I would really like to switch back to ART though because there are several apps that seem to run more smoothly with less stuttering during scrolling with ART enabled rather than Dalvik. I used ART with my 2013 Moto X with never an issue for nearly a year. Any words of advice or suggestions? I really don't want to have to get a replacement device... but I guess I will if I absolutely have to.
I had similar activity happen to me when switching to ART. Staying on Dalvik has eliminated any weird behavior except for the Hangouts force closing. I guess we have to wait on Google for an update.
What version do you have ? I have a XT1097 and its been 2 days with ART, 0 freeze or feboots
Faruko said:
What version do you have ? I have a XT1097 and its been 2 days with ART, 0 freeze or feboots
Click to expand...
Click to collapse
I have a 32GB Moto Maker variant on Verizon. XT1096.
I posted that I was getting shutdowns as well, with very few responses other than people telling me that they were not experiencing the same problem. I did however leave out that I was experiencing the problems while running on ART, and as some of you others have posted, after switching back to dalvik I have had no such issue. I also prefer ART but I will have to wait for an update I guess, which probably will not be until we get the upcoming Android L.
I should also mention that it seemed as though I was only getting the freezes/shutdowns while at work, where I have poor cell reception, yet I have wifi. Also, my phone is in my pocket all day and it does sway around a bit in my pocket. I am thinking this might make the IR sensors go a little crazy. Maybe the lack of cell reception and the IR sensors going crazy has something to do with it, if indeed having the phone in my pocket is messing with the sensors. You're not alone though. Stick with dalvik until we get an update.
stastnysnipes26 said:
I posted that I was getting shutdowns as well, with very few responses other than people telling me that they were not experiencing the same problem. I did however leave out that I was experiencing the problems while running on ART, and as some of you others have posted, after switching back to dalvik I have had no such issue. I also prefer ART but I will have to wait for an update I guess, which probably will not be until we get the upcoming Android L.
I should also mention that it seemed as though I was only getting the freezes/shutdowns while at work, where I have poor cell reception, yet I have wifi. Also, my phone is in my pocket all day and it does sway around a bit in my pocket. I am thinking this might make the IR sensors go a little crazy. Maybe the lack of cell reception and the IR sensors going crazy has something to do with it, if indeed having the phone in my pocket is messing with the sensors. You're not alone though. Stick with dalvik until we get an update.
Click to expand...
Click to collapse
Well that's disappointing... hopefully history will repeat itself and we'll see Android L sooner rather than later. I'd really like to be able to use ART again.
I'm willing to bet the 2014 moto x will be the first device after nexus devices to get android l.
Sent from my XT1096 using Tapatalk
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
So, I successfully clear the cache, I even clear the storage data with Google service and play store etc, and the phone runs smoothly for a while.
Until some app are updated, the whole phone goes crazy again, especially my camera. If I launch the moto camera (not any other camera app) and turn it off. All my app in background would be shut down, such as bluelight filter, every time! I have to reboot my phone, to make it turn back to normal, but at certain point, the phone would go crazy again with that camera issue!
I guess it is the problem with the incompatibility of 5.0, and in fact some apps do! I uninstalled a lot of them, but the issue goes on. This is my second week with my brand new moto x, but everything so far make me love my first moto x deeper!
Anyone can help?
alan547 said:
So, I successfully clear the cache, I even clear the storage data with Google service and play store etc, and the phone runs smoothly for a while.
Until some app are updated, the whole phone goes crazy again, especially my camera. If I launch the moto camera (not any other camera app) and turn it off. All my app in background would be shut down, such as bluelight filter, every time! I have to reboot my phone, to make it turn back to normal, but at certain point, the phone would go crazy again with that camera issue!
I guess it is the problem with the incompatibility of 5.0, and in fact some apps do! I uninstalled a lot of them, but the issue goes on. This is my second week with my brand new moto x, but everything so far make me love my first moto x deeper!
Anyone can help?
Click to expand...
Click to collapse
Check out this thread where we are discussing this issue. Seems to happen on KitKat too, and it seems to be a Motorola Camera issue. Download the Google Camera and use that in the meantime.
http://forum.xda-developers.com/mot...background-t2975234/post57594303#post57594303
havanahjoe said:
Check out this thread where we are discussing this issue. Seems to happen on KitKat too, and it seems to be a Motorola Camera issue. Download the Google Camera and use that in the meantime.
http://forum.xda-developers.com/mot...background-t2975234/post57594303#post57594303
Click to expand...
Click to collapse
Thank you!
if I remember correctly, I have no problem with 4.4.4. The camera issue is that something stopped the twist launch first, than I have to launch it manually, but soon the camera shut down by itself, and all my apps crashed, and relaunch.
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