Camera ONLY works in safe mode - Nexus 5 Q&A, Help & Troubleshooting

Hello guys
Please excuse me if this has already been posted before!
I've heard things about the camera not working in 4.4.4. Mine doesn't as well - only in safe mode. No matter what. Then I tried to pinpoint a 3rd party app that could've blocked the camera, both the back and the front (mostly front), but the issue keeps getting on top. I just rooted my N5 and installed PA, and the issue is still on! I haven't even installed the G-apps yet.
Any ideas?
Thank you so much!

install the gapps, but do not install/restore your other apps yet! try to see if the cam works. if so, install your apps after. to me it sounds as an app is causing you issues. btw, have you tried clearing the camera apps data? and by not working, what error do you get?

Install a different kernel PA uses stock Google kernel

spinninbsod said:
Install a different kernel PA uses stock Google kernel
Click to expand...
Click to collapse
what does the stock kernel have to do with the camera not working??? the right answer is absolutely nothing.

Because the kernel connects the hardware to the software and the kernel has all the drivers in it

spinninbsod said:
Because the kernel connects the hardware to the software and the kernel has all the drivers in it
Click to expand...
Click to collapse
so, all those unrooted nexus 5, running stock kernels, all have non working cameras? lol!

Well do you have any other reason maybe it is just an isolated incident with his specific device with the kernel maybe it's not functioning properly

spinninbsod said:
Well do you have any other reason maybe it is just an isolated incident with his specific device with the kernel maybe it's not functioning properly
Click to expand...
Click to collapse
A kernel has nothing to do with the camera, or do you have proof that it does?

Well if the kernel has nothing going to do with the camera what does?

spinninbsod said:
Well do you have any other reason maybe it is just an isolated incident with his specific device with the kernel maybe it's not functioning properly
Click to expand...
Click to collapse
well, the probability that its something else besides the kernel is off the charts. most likely it is an app, or corrupt data. actually, in my 6 years with android, not once have i seen a camera issue caused by the stock kernel. now a custom kernel can have issues with the cam, but thats usually because something was forgotten to be added. oh, and a rom can cause camera issue, which is the #2 spot of where his issue might come from. many times i have seen custom roms forget to add in all the needed camera libs.
---------- Post added at 03:57 PM ---------- Previous post was at 03:56 PM ----------
spinninbsod said:
Well if the kernel has nothing going to do with the camera what does?
Click to expand...
Click to collapse
the libs for the camera, which comes from the rom, which people forget to add to their roms often enough.

you have not right camera blobs

that very well could be as well..

simms22 said:
install the gapps, but do not install/restore your other apps yet! try to see if the cam works. if so, install your apps after. to me it sounds as an app is causing you issues. btw, have you tried clearing the camera apps data? and by not working, what error do you get?
Click to expand...
Click to collapse
Thanks for your reply! I'll try this right away. Is there any way I can install the Google Play market without having the Gapps? Otherwise I'll try to go for the minor Gapps ibcluding the most important ones - if of course it happens to work without it.
Clearing data causes it to say that it cannot connect to the camera!

Bad news. Clean PA Install - no Gapps and the problem is still on my agenda!
Any other suggestions? It cannot be hardware; why else would it work in safe mode?

Related

[SOLVED]Camera has a weird bug

Hello,
2 weeks ago my phone started to have a strange behaviour:
Every third photo i took was okay, like everytime, but the rest was broken. Basically they wont show any kind of picture information as well as on the device and on the computer.
Im on the latest ViperS ROM and Bricked kernel 1.4, the rest of the device works perfectly.
Any ideas?
Latest vipers? As in the jellybean version? 3.0.0 has no working camera yet. Devs are working on it. If you're on 1.6.3, try a different kernel, or try fix permissions. If these don't help, you might have developed a hardware fault. That won't be possible to fix.
Need to ask. Do you mean it takes a picture but the picture doesn't show up when you go back to look at it or the tags from the image are missing?
icanttinkofaname said:
Latest vipers? As in the jellybean version? 3.0.0 has no working camera yet. Devs are working on it. If you're on 1.6.3, try a different kernel, or try fix permissions. If these don't help, you might have developed a hardware fault. That won't be possible to fix.
Click to expand...
Click to collapse
No, i use ICS.
DennisBold said:
Need to ask. Do you mean it takes a picture but the picture doesn't show up when you go back to look at it or the tags from the image are missing?
Click to expand...
Click to collapse
The imagefile is there, but it is broken.
By the way, deleting dalvik cache and the normal cache seems to have solved the problem Thanks guys!

[Q] Camera

Camera just doesn't start..
its unpredictable it can start it may not load up after selection camera app..
it just starts for a second the entire view finder is black with all the options inactive and just closes with no message...
I am Viper Xl 4.2 and Elemental kernel 8.2
surprisingly i had the same problem on the previous rom i was using which was 'Cleanstrip' based on T mobile German release.
can anyone help?
besides GIF mode doesn't work...
Did you try with the stock kernel for ViperXL?
Are you s-on or s-off? I don't recall. Sounds like it might be a kernel mismatch to me.
redpoint73 said:
Did you try with the stock kernel for ViperXL?
Are you s-on or s-off? I don't recall. Sounds like it might be a kernel mismatch to me.
Click to expand...
Click to collapse
well i did try the stock kernel... it worked the same..
the thing is when i was on clean strip rom which is an offical build for our device,i had everything stock i wasn't even rooted still i had the issue.
and ya i am on SOFF!
the camera does work after several attempts i can click pictures but then i cant use GIF mode it FCs.
Have you done full wipes between ROMs?
Sent from my Evita
GIF mode? Do you mean the Zoe presentations? Are you installing the camera mod?
---------- Post added at 02:04 PM ---------- Previous post was at 02:03 PM ----------
timmaaa said:
Have you done full wipes between ROMs?
Click to expand...
Click to collapse
Yes, always make sure you do the default wipes in TWRP (factory reset, Dalvik and cache) when flashing a new ROM. Random bugs are often caused by failure to wipe.
redpoint73 said:
GIF mode? Do you mean the Zoe presentations? Are you installing the camera mod?
Click to expand...
Click to collapse
The camera contained in the Zoe mod has a gif mode, to make animated gif images. I'm guessing yes.
Sent from my Evita
timmaaa said:
The camera contained in the Zoe mod has a gif mode, to make animated gif images. I'm guessing yes.
Sent from my Evita
Click to expand...
Click to collapse
ya the ZOE feature on Sense 5 4.2.2 havent flashed any mod it jus came with every ROM i had on my device!
ya i did wipes prior to installation...
i also tried to go for fixing permissions as well but its still unpredictable..
everything works when the camera starts the zoom and the video also the simultaneous capture but not the GIF mode just FCs the entire camera app.
besides the camera also doesn't start from other means like if i want to share an image from whatsapp.
redpoint73 said:
GIF mode? Do you mean the Zoe presentations? Are you installing the camera mod?
---------- Post added at 02:04 PM ---------- Previous post was at 02:03 PM ----------
Yes, always make sure you do the default wipes in TWRP (factory reset, Dalvik and cache) when flashing a new ROM. Random bugs are often caused by failure to wipe.
Click to expand...
Click to collapse
i did that! :good:
It seems that the Zoe GIF feature is broken on ViperXL 4.2. You can flash the Zoe camera mod to get the GIF feature back. But it will break camera zoom: http://forum.xda-developers.com/showthread.php?t=2436347
Read or search the ViperXL thread for details.
Not sure if the issue with the camera app not starting is related, or not.
redpoint73 said:
It seems that the Zoe GIF feature is broken on ViperXL 4.2. You can flash the Zoe camera mod to get the GIF feature back. But it will break camera zoom: http://forum.xda-developers.com/showthread.php?t=2436347
Read or search the ViperXL thread for details.
Not sure if the issue with the camera app not starting is related, or not.
Click to expand...
Click to collapse
i will try that orelse go for a third party camera app!
thanks.
redpoint73 said:
It seems that the Zoe GIF feature is broken on ViperXL 4.2. You can flash the Zoe camera mod to get the GIF feature back. But it will break camera zoom: http://forum.xda-developers.com/showthread.php?t=2436347
Read or search the ViperXL thread for details.
Not sure if the issue with the camera app not starting is related, or not.
Click to expand...
Click to collapse
surprisingly the third party camera app also dint work.
i tried focal as well...
btw abt ZOE mod the link u sent me,i just read the thread some dev did say that zoom got fixed?
Sonone said:
surprisingly the third party camera app also dint work.
i tried focal as well...
Click to expand...
Click to collapse
Not particularly surprising to me. Although these are 3rd party camera apps, they must still use the phone's drivers and other low-level resources.
You might try to do a full wipe (factory reset, Dalvik and cache) and flash a different ROM (maybe stock rooted), just to make sure its not the ROM or kernel, and to be sure you did the required wipes. Or maybe even RUU back to stock, which would be a bit of a pain, since you would have to then install TWRP again, and flash the 2.15 firmware to get back to where you are now.
But if you RUU, and the problem still persists, it may indicate a hardware problem. But it seems too coincidental to me, since you have been messing with ROMs and kernels, and the if the camare worked before, its more likely just a software issue.
Sonone said:
btw abt ZOE mod the link u sent me,i just read the thread some dev did say that zoom got fixed?
Click to expand...
Click to collapse
I haven't been following that thread, as I don't use the mod. Its best you read through the thread yourself, and determine what is the most recent and relevant information. Or ask in the thread yourself, if its still not clear. It seemed to me when I was reading it (its been a couple weeks), that zoom was fixed for a short while, but may have led to some other issues. Then it went back to zoom being broken. But I haven't been keeping up lately, and it may have been fixed again.
redpoint73 said:
Not particularly surprising to me. Although these are 3rd party camera apps, they must still use the phone's drivers and other low-level resources.
You might try to do a full wipe (factory reset, Dalvik and cache) and flash a different ROM (maybe stock rooted), just to make sure its not the ROM or kernel, and to be sure you did the required wipes. Or maybe even RUU back to stock, which would be a bit of a pain, since you would have to then install TWRP again, and flash the 2.15 firmware to get back to where you are now.
But if you RUU, and the problem still persists, it may indicate a hardware problem. But it seems too coincidental to me, since you have been messing with ROMs and kernels, and the if the camare worked before, its more likely just a software issue.
I haven't been following that thread, as I don't use the mod. Its best you read through the thread yourself, and determine what is the most recent and relevant information. Or ask in the thread yourself, if its still not clear. It seemed to me when I was reading it (its been a couple weeks), that zoom was fixed for a short while, but may have led to some other issues. Then it went back to zoom being broken. But I haven't been keeping up lately, and it may have been fixed again.
Click to expand...
Click to collapse
If I may. I have been flashing custom ROMs since July of last year on this device (AOSP, Sense, and everything in between) and as of late, I am having a camera FC also. I am S-OFF, Hboot 2.14, TWRP 2.6.0, and running CM 10.2 latest nightly. I have tried RUUing, MagioRom 4.0.2, Rage (because its 4.1.2), CM 10.1, and none of them produce a working camera. What's weird is that right after flashing a new rom, the camera works. It even takes pictures. But the second or third attempt to use the camera produces an FC. Sometimes is says, "Cannot connect to the camera." Other times it's, "Gallery has stopped working." Everything else is running great on the phone. I did a logcat, but i cannot find it.
Great!
redpoint73 said:
Not particularly surprising to me. Although these are 3rd party camera apps, they must still use the phone's drivers and other low-level resources.
You might try to do a full wipe (factory reset, Dalvik and cache) and flash a different ROM (maybe stock rooted), just to make sure its not the ROM or kernel, and to be sure you did the required wipes. Or maybe even RUU back to stock, which would be a bit of a pain, since you would have to then install TWRP again, and flash the 2.15 firmware to get back to where you are now.
But if you RUU, and the problem still persists, it may indicate a hardware problem. But it seems too coincidental to me, since you have been messing with ROMs and kernels, and the if the camare worked before, its more likely just a software issue.
I haven't been following that thread, as I don't use the mod. Its best you read through the thread yourself, and determine what is the most recent and relevant information. Or ask in the thread yourself, if its still not clear. It seemed to me when I was reading it (its been a couple weeks), that zoom was fixed for a short while, but may have led to some other issues. Then it went back to zoom being broken. But I haven't been keeping up lately, and it may have been fixed again.
Click to expand...
Click to collapse
thanks as always....
Hardware issue = Horror!!
as i said i have just tried 3 roms the first being the Sense 4.2.2 stock.. then clean strip and then Viper Xl 4.2 and then finally i flashed Elemental Kernel 8.2..
i did try wiping cache and dalvik and also did fix permissions..
but as i said its unpredictable behavior
!
HOXnoo8 said:
If I may. I have been flashing custom ROMs since July of last year on this device (AOSP, Sense, and everything in between) and as of late, I am having a camera FC also. I am S-OFF, Hboot 2.14, TWRP 2.6.0, and running CM 10.2 latest nightly. I have tried RUUing, MagioRom 4.0.2, Rage (because its 4.1.2), CM 10.1, and none of them produce a working camera. What's weird is that right after flashing a new rom, the camera works. It even takes pictures. But the second or third attempt to use the camera produces an FC. Sometimes is says, "Cannot connect to the camera." Other times it's, "Gallery has stopped working." Everything else is running great on the phone. I did a logcat, but i cannot find it.
Great!
Click to expand...
Click to collapse
In my case it is a bit different!
well the camera doesn't force close (by which i mean there is no message displayed)
it starts-> the menu loads up instantaneously -> the thumbnails may or may not load (at the bottom most corner) -> and it abruptly closes -> after 3 4 times it does start eventually......
the phone is very stable after the abrupt stopping of camera..
and my gallery is fine....
i dint get a message on focal as well it just doesn't load up there..

[Q] Nexus 5 reboots reason kernel_panic & wdog_bite

I am annoyed by this random reboot issue still being unsolved.
Please if someone can help with troubleshooting the errors in last_kmsg:
"unable to handle the NULL pointer dereference at virtual address...... "
"unable to handle the paging request at virtual address........"
I am not an expert but I have read on the Internet about Linux kernel "oops" leading to kernel panic and reboot.
Can anyone build a fix for the Android kernel to handle these oops errors and not panic? Or can anybody read these last_kmsg files and tell me what is causing this?
last_kmsg files attached.
im going to check them out shortly, but kernel panics can be caused by just about anything. even a simple derp, will lead to a kernel panic, which will lead to a reboot.
---------- Post added at 07:04 PM ---------- Previous post was at 06:55 PM ----------
Zaeem Adil said:
I am annoyed by this random reboot issue still being unsolved.
Please if someone can help with troubleshooting the errors in last_kmsg:
"unable to handle the NULL pointer dereference at virtual address...... "
"unable to handle the paging request at virtual address........"
I am not an expert but I have read on the Internet about Linux kernel "oops" leading to kernel panic and reboot.
Can anyone build a fix for the Android kernel to handle these oops errors and not panic? Or can anybody read these last_kmsg files and tell me what is causing this?
last_kmsg files attached.
Click to expand...
Click to collapse
if youre using avast security software, i think its causing it, or is playing a role in it. but thats my guess, not 100%.
simms22 said:
im going to check them out shortly, but kernel panics can be caused by just about anything. even a simple derp, will lead to a kernel panic, which will lead to a reboot.
---------- Post added at 07:04 PM ---------- Previous post was at 06:55 PM ----------
if youre using avast security software, i think its causing it, or is playing a role in it. but thats my guess, not 100%.
Click to expand...
Click to collapse
Thanks
I am currently using avast but these kernel_panics occur without any 3rd party app installed at all.
are you completely stock? the kernel panics occur not because of the kernel, it just reacts to the oops. anything, including rim, apps, data flow, your router, etc can cause them. sounds like you get them often, which you shouldnt. if rarely, then id say it was normal, but often isnt normal.
oh, i said avast because it shows up twice, right before stuff goes wrong.
simms22 said:
are you completely stock? the kernel panics occur not because of the kernel, it just reacts to the oops. anything, including rim, apps, data flow, your router, etc can cause them. sounds like you get them often, which you shouldnt. if rarely, then id say it was normal, but often isnt normal.
oh, i said avast because it shows up twice, right before stuff goes wrong.
Click to expand...
Click to collapse
Yes I am completely stock and yes I get reboots very often. Please guide me how to get to the actual culprit which is causing this. I have uninstalled avast.
I got 3 reboots in last 5 minutes here are the logs.
Zaeem Adil said:
I got 3 reboots in last 5 minutes here are the logs.
Click to expand...
Click to collapse
Flash some other kernel. If it doesnt work its either rom or hardware related
lolerpro8 said:
Flash some other kernel. If it doesnt work its either rom or hardware related
Click to expand...
Click to collapse
I have used Franco kernel on stock 4.4.4 and I even tried CM11 the problem persisted in both situations. Suggest me some better kernel I'll try it.
try without any custom kernel, stock kernel.. problem persists? go get an RMA, its not supposed to be happening. actually, i have never seen so many wdog bites!
Zaeem Adil said:
I have used Franco kernel on stock 4.4.4 and I even tried CM11 the problem persisted in both situations. Suggest me some better kernel I'll try it.
Click to expand...
Click to collapse
Flash factory images. If it doesn't work its hardware related
lolerpro8 said:
Flash factory images. If it doesn't work its hardware related
Click to expand...
Click to collapse
this. if still happening, go get it exchanged.
lolerpro8 said:
Flash factory images. If it doesn't work its hardware related
Click to expand...
Click to collapse
I flashed factory images and the issue is still there. There is an app named stability test on play store it runs several stress tests on the cpu at different frequencies and also on the ram. I ran it and during the tests the device temp got up to 45 degrees and even after 50 successfull cpu runs on all the 4 cores and 500 successful ram runs the device didn't reboot. If it is hardware related why does it pass the stress test over n over again? One thing more, the device reboots most of the time when it is connected to internet through wifi or mobile data. I am doubtful that it is something related to the modem drivers. I found stock flashable radio images n i flashed them but the problem is still there.
Zaeem Adil said:
I flashed factory images and the issue is still there. There is an app named stability test on play store it runs several stress tests on the cpu at different frequencies and also on the ram. I ran it and during the tests the device temp got up to 45 degrees and even after 50 successfull cpu runs on all the 4 cores and 500 successful ram runs the device didn't reboot. If it is hardware related why does it pass the stress test over n over again? One thing more, the device reboots most of the time when it is connected to internet through wifi or mobile data. I am doubtful that it is something related to the modem drivers. I found stock flashable radio images n i flashed them but the problem is still there.
Click to expand...
Click to collapse
When you talk about hardware problems you can only speculate. There is most likely cpu related. If it was software related, flashing other fitmware would fix the problem. Since it doesn't the only answer is hardware
https://www.dropbox.com/s/j7o39s38anhc7cy/2014-08-17_08.13.zip
Sent from my Nexus 5 using XDA Premium 4 mobile app

Oneplus one running nightly Lineage os reboots after camera is used

Just recently updated to the most recent update of Lineage os for the opo, lineage 14.1 20170717. I'm now having issues with the camera, when I open the camera and close it, it completely reboots the phone. Is this just a problem with this nightly or has anyone else had issues with this? Let me know if you have any suggestions, for now ill just have to revert back to the previous nightly build and hope that works.
Similar camera problem
xstewminator said:
Just recently updated to the most recent update of Lineage os for the opo, lineage 14.1 20170717. I'm now having issues with the camera, when I open the camera and close it, it completely reboots the phone. Is this just a problem with this nightly or has anyone else had issues with this? Let me know if you have any suggestions, for now ill just have to revert back to the previous nightly build and hope that works.
Click to expand...
Click to collapse
Similar experience with this nightly build, camera worked fine initially with no changes to the settings on the pull out menu on the left. After customizing these settings my camera crashes on initializing and will not start at all.
to the OP, please report how reverting to the previous nightly is working for you.
Foxjet said:
Similar experience with this nightly build, camera worked fine initially with no changes to the settings on the pull out menu on the left. After customizing these settings my camera crashes on initializing and will not start at all.
to the OP, please report how reverting to the previous nightly is working for you.
Click to expand...
Click to collapse
Unfortunately same here... after taking a shot Im trying to watch the pic, phone freezes and than restarts.
suggestions?
Disabled the standard camera
Lalon80 said:
Unfortunately same here... after taking a shot Im trying to watch the pic, phone freezes and than restarts.
suggestions?
Click to expand...
Click to collapse
I have disabled the camera via settings, apps. and installed Open Camera from the Play Store. This seems to be working fine and I like the Open Camera app.
Is there a downside to what I have done? Yes, I am not very experienced and want to learn.
Foxjet said:
Similar experience with this nightly build, camera worked fine initially with no changes to the settings on the pull out menu on the left. After customizing these settings my camera crashes on initializing and will not start at all.
to the OP, please report how reverting to the previous nightly is working for you.
Click to expand...
Click to collapse
Sorry for the super long delay (went out of country), the previous nightly hasn't helped at all, im thinking it may be a physical issue with the camera. But im gonna see if i can do what @Foxjet tried and see if that works for me. I'll let you guys know if and when i find a solution.
Even in my OPO running with latest update of nightly bacon, my default camera app keeps on crashing. It says "camera keeps stopping". Please I need a solution for this.
Srikar7852 said:
Even in my OPO running with latest update of nightly bacon, my default camera app keeps on crashing. It says "camera keeps stopping". Please I need a solution for this.
Click to expand...
Click to collapse
Clean flash the rom again.
Mr.Ak said:
Clean flash the rom again.
Click to expand...
Click to collapse
In that case i would lose all my data, could u plz suggest me another way!!!
Read the whole thread!
Srikar7852 said:
In that case i would lose all my data, could u plz suggest me another way!!!
Click to expand...
Click to collapse
I think you are right, clean flashing would be a waste of time and general pain in the ass.
I clean flashed the July 17 nightly and my camera app did the same thing yours is doing after I customized the settings accessed by pulling out the menu on the left side of the camera interface.
I then installed Open Camera from the Playstore and disabled the original camera app. It's working well.
I recently dirty flashed the July 24 nightly and rechecked the original camera app which still will not open due to crashing, so I disabled it again.
I think there was something listed in the upcoming items for the next nightly about a camera mod that may address this issue.
Foxjet said:
I think you are right, clean flashing would be a waste of time and general pain in the ass.
I clean flashed the July 17 nightly and my camera app did the same thing yours is doing after I customized the settings accessed by pulling out the menu on the left side of the camera interface.
I then installed Open Camera from the Playstore and disabled the original camera app. It's working well.
I recently dirty flashed the July 24 nightly and rechecked the original camera app which still will not open due to crashing, so I disabled it again.
I think there was something listed in the upcoming items for the next nightly about a camera mod that may address this issue.
Click to expand...
Click to collapse
Thnx for the suggestion. But I tried disabling my camera in SettingsAppsCamera. But the disable doesn't come up. I couldn't disable it. And open camera app doesn't run until i disable this older one!!
Srikar7852 said:
Thnx for the suggestion. But I tried disabling my camera in SettingsAppsCamera. But the disable doesn't come up. I couldn't disable it. And open camera app doesn't run until i disable this older one!!
Click to expand...
Click to collapse
In that case, I would consider the previous advice and do a clean flash.
Do a Nandroid backup, back up your contacts, photos, etc separately and reflash. I see there is a new nightly available dated July 31 , I'm going to try it and see if the camera app behaves any differently. I'm not sure at this point if I should let it do the automatic update or download and clean flash.
Any advice from the more experienced ?
Foxjet said:
In that case, I would consider the previous advice and do a clean flash.
Do a Nandroid backup, back up your contacts, photos, etc separately and reflash. I see there is a new nightly available dated July 31 , I'm going to try it and see if the camera app behaves any differently. I'm not sure at this point if I should let it do the automatic update or download and clean flash.
Any advice from the more experienced ?
Click to expand...
Click to collapse
Thnx fr ur time!!
Srikar7852 said:
Thnx fr ur time!!
Click to expand...
Click to collapse
Yeah!! Clean flashing the latest update fixed my problem!!
its a bug.. The only way to get it to work is to clear the cache and data cache. Download the Open Camera app or CameraMx.

Both cams failure

Hi there,
I got a problem with my Nexus 5 32GB (D821). Frist the rear cam failured, now the frontcam failured.
I tried another rear cam modul, doesnt work.
I tested the cam modul with another nexus - it works. I tried the cam modul of the first one - it works.
So the cam modules are fine.
I tried a lot of apps, none of them worked. I've tried another custom rom - nothing changed.
Of course I deleted the cache and stoped the app.
Got anybody an idea whats wrong with my Nexus?
Have you wiped and flashed the latest stock ROM? If the camera still doesn't work, it may be a failed motherboard.
audit13 said:
Have you wiped and flashed the latest stock ROM? If the camera still doesn't work, it may be a failed motherboard.
Click to expand...
Click to collapse
Hi audit13 thank you for your response..
Yes, I flashed the last stock... but... there is no google camera app installed... and I can't find it in the Playstore...
Other App like OpenCamera can't connecting to the cameras..
There's no camera app after flashing the stock Google ROM? Strange because I recall that every Google ROM I flashed via fastboot had a camera app.
audit13 said:
There's no camera app after flashing the stock Google ROM? Strange because I recall that every Google ROM I flashed via fastboot had a camera app.
Click to expand...
Click to collapse
I whipped again... you're right. The google cam app is already installed but the icon is missing and I can't start the cam.
Other apps doesn't work.
But after I try the spare part again the front cam is working again..
Maybe there is a bad connection on there motherboard? Try cleaning the connection with pure isopropyl alcohol?
audit13 said:
Maybe there is a bad connection on there motherboard? Try cleaning the connection with pure isopropyl alcohol?
Click to expand...
Click to collapse
I did... but nothing has changed... but now I can try to start the google cam app... but it ends with the old failure...
Sounds like a motherboard replacement may be required.
audit13 said:
Sounds like a motherboard replacement may be required.
Click to expand...
Click to collapse
Thats pitty... but I guessed something in this way...
Thank you for your help

Categories

Resources