Hi folks,
I have recently had an issue with the Moto G 2nd gen ONLY since yesterday with the Camera (Moto Camera app). I had been able to use the camera in the morning.
I tested with other apps which access the camera such as Instagram. Instagram could not start taking photo at all.
I don't know for what reason, the camera cannot start any longer. I tried to wipe the cache but it did not help at all. I am running standard Moto Android 5.0.2, with no custom firmware installed at all.
Does anyone know what is happening to my phone?
Thanks a lot for looking.
Try going to setings-->apps-->all, choose camera,delete cache,delete data,uninstall updates and stop the app. Reboot the device,try if camera app works. If yes install updates from playstore. If this doesn´t work boot the phone into recovery and delete cache partition. Maybe try first procedure again.If you are rooted you can try to uninstall camera via Titanium and install again.
Wolfcity said:
Try going to setings-->apps-->all, choose camera,delete cache,delete data,uninstall updates and stop the app. Reboot the device,try if camera app works. If yes install updates from playstore. If this doesn´t work boot the phone into recovery and delete cache partition. Maybe try first procedure again.If you are rooted you can try to uninstall camera via Titanium and install again.
Click to expand...
Click to collapse
Thanks for your suggestion :good:. I've done all of those steps. Even, I came to a point wipe all data and factory reset. No app installed rather than what comes with the phone. I still have the same error. Does it mean the camera has been physically broken?
Alright guys, I had to talk to Motorola Support about my case last week. After a long chat, I have it repaired under the warranty policy. I just received it back now. The camera was replaced due to hardware issue. Case closes here guys, thanks for the help so far.
Related
Hi All,
Running stock but rooted (with Xposed modules) 4.4.4 on Verizon Moto X with an unlocked bootloader. (Flashed this stock ROM: http://forum.xda-developers.com/showthread.php?t=2829123 )
Any time I try to do any activity with voice I get the error, "Can't reach google at the moment."
I get this error if I click the mic in google now and by clicking the voice text mic on the keyboard. Also, Touchless Controls doesn't respond.
After searching around forums I've tried some suggestions that worked with similar problems on other phones, but to no avail. I've tried:
- clearing data and cache of google search app and force stopping (lost my google now launcher set up in the process)
- removing my google account from the phone, rebooting to recovery, clearing cache and dalvik, rebooting and adding my account back
Thanks for any suggestions.
hi, had the same issue with one of the modules in xposed, ended up wipping the device and started fresh, installed xposed and gravity box, no other modules, all is good now.
ericizzy1 said:
hi, had the same issue with one of the modules in xposed, ended up wipping the device and started fresh, installed xposed and gravity box, no other modules, all is good now.
Click to expand...
Click to collapse
Hmm, interesting...
I'm thinking it's not a specific Xposed module... I just tried uninstalling xposed framework altogether and then wiping cache and dalvik for good measure. No luck.
But out of curiousity, these are the modules I have installed: GravityBox, Exchange Bypass For Xposed, SingalIconsAOSP, Unicon. Besides GravityBox, did you have any of these installed when you had the issue?
I hope this doesn't come down to just wiping, which it most likely will.
My droid maxx has had the same problem since the update to 4,4,4 I have tried everything including a fdr ( through twrp ). Nothing has worked ! Moto has offered me a new phone but I don't want a new one as mine is unlocked and rooted ( otherwise stock ). I think I'm going to unroot it, put back in the stock recovery and try a fdr through that...POS !!!
This may not help at all....but maybe worth a shot. If you try and it doesn't help, post back here and let everyone know so nobody else tries it.
You might have some luck by erasing baseband cache with fastboot:
fastboot erase modemst1
fastboot erase modemst2
You might have to re-activate afterwards. It is the only suggestion that might be relevant that you haven't tried already...
Good Luck....that would be a frustrating issue... :good:
Unfortunately I gave up and just wiped and did another clean flash and its working again. It was very frustrating not having touch less controls or voice to text...
Thanks for the help though anyway.
leffer said:
Unfortunately I gave up and just wiped and did another clean flash and its working again. It was very frustrating not having touch less controls or voice to text...
Thanks for the help though anyway.
Click to expand...
Click to collapse
I agree touch less control wasn't something I cared about when I got the phone. But after getting used to it its hard to go without.
When you say you wiped and flashed. Can you elaborate. I tried fxzing ( saving data ), 2 FDR's everything .. Did you unroot then use HOM ? I will try anything at this point . Thanks in advance
tombaldwin6 said:
I agree touch less control wasn't something I cared about when I got the phone. But after getting used to it its hard to go without.
When you say you wiped and flashed. Can you elaborate. I tried fxzing ( saving data ), 2 FDR's everything .. Did you unroot then use HOM ? I will try anything at this point . Thanks in advance
Click to expand...
Click to collapse
My bootloader is unlocked so I was able to simply factory reset and reflash the stock 4.4.4 ROM from the thread I linked to in the OP...
leffer said:
My bootloader is unlocked so I was able to simply factory reset and reflash the stock 4.4.4 ROM from the thread I linked to in the OP...
Click to expand...
Click to collapse
I will try both methods and post back. Thanks for you help !
So I took both suggestions tried them 1st. I tried erasing the the baseband cache's via fastboot. No luck. 2nd I reflashed the current 4.4.4 stock rom via HOM, Full FXZ ( no data saved). !st off what a pain in the ass it is to reset up these phones from scratch. I setup my Google account but I didn't let Google reinstall all my previous apps and there data. I then went into settings and arranged things how I like them. Cleared off my home screens, put a few of the apps where I wanted them. I then went into the play store and allowed all apps ( preloaded ) to update. I then went back into settings and went to touchless control. To my surprise it worked ! I then went about loading all my apps.The usual 1's everyone has ie: Elixir2, FX filemanager,Poweramp, MX Player,Chromecast Panasonic tv remote 2, Google Wallet, UE Miniboom and Few other nondescript. Then I checked touchless control again and It was still working. Then I decided to install twrp and its recovery via fastboot ( 2.6.31 ) let it root the phone for me. Here's where it gets dicey.. It was late and I had had it with this friggin phone. I went and loaded all my apps that required root,Superuser pro, Dsploit, Busybox pro,Android terminal emulator, Wakelock(full) all the usual's. Then I went through and disabled all of the bloat. Rebooted and switched the phone to ART The following morning I went to show a friend how I had fixed my phone and It no longer worked ?
So I FXZ'd again not saving any data. Reinstalled twrp , rooted . Then 1 by 1 I reloaded every single app back into the phone and checked google now between every single install. Also this time I didn't let any of the bloatware update. I planned on disabling it anyways so why bother. I didn't install any apps that require root except twrp, busybox, Dsploit and #mirrorenabler . Also it's currently back on Dalvic. So as my phone sits now touchless control and all of its functions are working again. It's obviously a rouge app or ART Runtime that did this and I will narrow it down in the next few days and report back.
motorola x xt1052 camera clarity wrost after flashing to cm 12.1 , gapps r stopped working,
malli8043 said:
motorola x xt1052 camera clarity wrost after flashing to cm 12.1 , gapps r stopped working,
Click to expand...
Click to collapse
To use Stock camera, you've to be in Stock ROM.
May be you'll need to check and flash another set of Gapps or wipe cache
@malli8043 hi, I'm having the same issues with the camera crashing on and on. I've been trying to change settings, cleared cashe, cleaned up dalvik, but ended up getting the error after a while. I installed a different rom (from Lineage 6.1 to Mokee) But after the optimization of the applications it stops working. The problem is that the front camera only works on, but the back camera has some issues with. I opened a discussion on this but no one is answering.
dritank said:
@malli8043 hi, I'm having the same issues with the camera crashing on and on. I've been trying to change settings, cleared cashe, cleaned up dalvik, but ended up getting the error after a while. I installed a different rom (from Lineage 6.1 to Mokee) But after the optimization of the applications it stops working. The problem is that the front camera only works on, but the back camera has some issues with. I opened a discussion on this but no one is answering.
Click to expand...
Click to collapse
No one is answering...without offence, dude, your cross posting is kinda spam, and will lead you to nowhere! Let's say, more honesty, that you already got your answer, but maybe you didn't like it. For example, I personally adviced you to erase everything in your phone and perform a fully clean flash... Your problem doesn't exist on board the other moto x, do you understand it? So, no one could give you an answer about the how and why you experience such issue. Erase everything, also internal memory, then flash rom + gapps! Good luck
Hi @stefanowall, I didn't get any answer and I'm still waiting for one. I did twice a full clean flash, install the rom, install gapps(nano or pico) but it didn't work. Actually it stops working after the app updates, when it does the optimization of them, I did erase xposed framework, greenify, and all that was suspected in interfering. But the problem still persist. I think it is a binary that gets corrupted along with something else, or is a conflict of camera permission, because I don't understand why the camera settings are changed and only the front camera works, that's why I posted the pictures of the camera settings. The only solution I found was that I flashed a Motorola camera from Lolipop version and after that both cameras were working surprisingly. So I'm testing it now and will let you know if this works. But still I think that there is a conflict or a something like that...
---------- Post added at 05:53 AM ---------- Previous post was at 05:52 AM ----------
Hi @stefanowall, I didn't get any answer and I'm still waiting for one. I did twice a full clean flash, install the rom, install gapps(nano or pico) but it didn't work. Actually it stops working after the app updates, when it does the optimization of them, I did erase xposed framework, greenify, and all that was suspected in interfering. But the problem still persist. I think it is a binary that gets corrupted along with something else, or is a conflict of camera permission, because I don't understand why the camera settings are changed and only the front camera works, that's why I posted the pictures of the camera settings. The only solution I found was that I flashed a Motorola camera from Lolipop version and after that both cameras were working surprisingly. So I'm testing it now and will let you know if this works. But still I think that there is a conflict or a something like that...
Hello xda!
I'm a new member and I thought you guys could know about the issues I have on my Z3 Compact.
After using my phone a little while, I decided to root it so I unlocked it's BL. Then I tried rooting but couldn't. Well I could root it but I didn't want Kit Kat so I used it without root but with UBL for a while. Then I decided to root it. I rooted it successfuly and now I am using Wajk's 5.1.1 Stock Slim Rom. Ever since unlocking my bootloader I'm having issues. I turn on my phone, use it for sometime, then I can't watch videos from YouTube app. It says "There was a problem while playing. Touch to retry.". When YouTube stops working, I noticed that I also can't record videos with the camera and I can not play videos from the storage of my phone (any video). It says "Can't playback video". Only fix I found for this is I hold the Power Button + Vol. Up button to wipe dalvik cache. After that problem goes away. But still, after a while, it does the same thing. Any ideas what it might be?
Appreciate every effort from now...
Up Up!
Any answers?!
Try to find the dev and ask if there is an update if not find a new rom
Sent from my M3 using XDA-Developers mobile app
marshalpear said:
Hello xda!
I'm a new member and I thought you guys could know about the issues I have on my Z3 Compact.
After using my phone a little while, I decided to root it so I unlocked it's BL. Then I tried rooting but couldn't. Well I could root it but I didn't want Kit Kat so I used it without root but with UBL for a while. Then I decided to root it. I rooted it successfuly and now I am using Wajk's 5.1.1 Stock Slim Rom. Ever since unlocking my bootloader I'm having issues. I turn on my phone, use it for sometime, then I can't watch videos from YouTube app. It says "There was a problem while playing. Touch to retry.". When YouTube stops working, I noticed that I also can't record videos with the camera and I can not play videos from the storage of my phone (any video). It says "Can't playback video". Only fix I found for this is I hold the Power Button + Vol. Up button to wipe dalvik cache. After that problem goes away. But still, after a while, it does the same thing. Any ideas what it might be?
Appreciate every effort from now...
Click to expand...
Click to collapse
Not entirely sure why you would unlock your bootloader to root your phone. Have you tried re-locking it with the backup you made of the TA partition? That might fix your problem.
Another solution suggested is to go to settings\apps > Youtube > Force stop & Wipe data. Then restart your phone into recovery and wipe cache.
Have you tried re-installing flash? There is a youtube video that claims to fix it.
Have you tried enabling Use AwsomePlayer in the developer options.?
The video not working on your camera is broken bootloader symptoms. There is supposed to be a flashable fix but I don't know if it works or not.
Didgesteve said:
Not entirely sure why you would unlock your bootloader to root your phone. Have you tried re-locking it with the backup you made of the TA partition? That might fix your problem.
Another solution suggested is to go to settings\apps > Youtube > Force stop & Wipe data. Then restart your phone into recovery and wipe cache.
Have you tried re-installing flash? There is a youtube video that claims to fix it.
Have you tried enabling Use AwsomePlayer in the developer options.?
The video not working on your camera is broken bootloader symptoms. There is supposed to be a flashable fix but I don't know if it works or not.
Click to expand...
Click to collapse
First of all thank you for your reply. I've tried everything that you stated and it seems to be a lollipop issue. I wanted to try custom ROMs and such that was the reason for me to unlock my bootloader, also I didn't know you could get root without unlocking BL, so I had done it without a backup or anything . But since I started using 6.0.1 the problem disappeared. Thank you for your kind efforts.
This is what I get from the built-in camera app of my about one week old XP. Drives me nuts. I have defrosted all the bloatware I had freezed with Titanium, because I thought that may have been the reason. But it wasn't. I have tried with a third party camera app from Play Store, and that works without problems. So does the Snapchat camera. So it's nothing hardware, it's something that ties up the app. I have tried to reset the camera app, wipe data for the app and wipe dalvik and regular cache from TWRP. Any ideas what else I can do?
Could you find any solution?
Apart from using a third party app, not so far.
i have same problem
how to fix it? still waiting
I think it's the rooting with Magisk! I will see if I can find the developer. Have you two rooted?
Oh, it's not the rooting in itself, it must be Magisk. I have now rooted with SR2-SuperSU-v2.79-SR2-20170103215521.zip, and that worked as it should. No camera malfunctions.
I have reported it in the Magisk forum.
I have done a full repair using xperia companion and it still won't work. I believe Magisk is still installed, but I've already tried uninstalling it so how would I make sure?
Once you've unlocked the bootloader, it must be unlocked in order to use the stock camera app on an official ROM
use custom kernel to fix the problem
nieXas said:
use custom kernel to fix the problem
Click to expand...
Click to collapse
The problem is that the camera doesnt work with a RE-LOCKED bootloader , flashing a custom kernel is not possible with a LOCKED/RELOCKED bootloader.
Hello, I do have a problem with my front camera. When trying to switch to the front camera within any camera app, the app freezes. I do not know when the problem started, but I noticed first on OOS 4.1.3. At first I thought it had to do with the custom kernel or some Magix mods. Because of that, I clean installed OOS 4.1.6 and only installed Magix (no mods, no kernel). The problem is still there. Does anyone know how to solve this problem? Or is it a hardware issue and I should send the phone to repair?
My specs in short:
OnePlus 3t (64gb Rom)
OOS 4.1.6
Magix v12
Stock kernel
Thank you in advance
At first, try just to clear app data for camera app/gallery app and see if that helps. Else you should do a factory restore of phone to see if problem still persist, in that case it's probably hardware fault.
pitrus- said:
At first, try just to clear app data for camera app/gallery app and see if that helps. Else you should do a factory restore of phone to see if problem still persist, in that case it's probably hardware fault.
Click to expand...
Click to collapse
Thank you for the answer, I tried to use different camera apps (stock app, opencamera, snapdragon camera), they all crashed when trying to use the front camera.
I already did a factory reset when clean installing the newest OOS.
I really hope, this isn't a hardware fault. The "Phone tester" app shows the camera features as it should.
Could there be a problem with TWRP flashing the roms making a mistake? TWRP didn't show an error through. I am on TWRP 3.1.0-1
There could be something wrong in the persistent partition causing this, reflashing factory persist.img to partition might fix it (easy way is to use qualcomm restore method which restores everything).
Thank you, I will try it next weekend, when I am back home ?