Develop Bugs

[Q] Camera and Gallery Stopped, Unfortunately

I've read about a million of these threads and researched elsewhere, but am coming back to the experts here.
The issue is that the camera won't work. It says, "unfortunately, gallery has stopped." We did clearing data. We did factory resets. I replaced both front and back cameras. I flashed the factory image.
After flashing the factory image, the phone boots up with "unfortunately gallery has stopped." I tried installing an old MIUI camera that supposedly only uses the back camera. It stops. Barcode Scanner stops. Trying to start a front facing hangouts session....stops. Downloaded some selfie camera app...stops.
Going to take it apart again and check connections. Any other ideas? Maybe the replacement parts from ifixit.com were bad? Or something else...
Thanks.

Ohh...
Previously it wouldn't charge. Changed the battery with an after market (non NFC) and USB FLEX cable. That all works good now...

Boot into recovery and wipe system, cache, data, internal, dalvik cache...and then flash factory image. You maybe didn't wiped all before flashing factory img..

Thanks...will gibe it a try. While I was at it, I also saw that recovery had repair option for some partitions.
Flashing now...

"Unfortunately Gallery has stopped...." right after the setup wizard started.

{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Both old cameras (top) and new (bottom) look good.

Contacts look good...buy will clean anyway.
A little corrosive damage on the chip cover.
Right next to the back camera contact is a gold surface with some black dots. Are the dots normal, or has something been worn away?

Now were getting somewhere!
Those black spots were some kind of mold/corrosion. Cleaned contacts and installed the old cameras and factory reset.
The camera actually opens now...but to a blackish/greyish screen. Different message now that gallery isn't responding.
Gonna wipe all, flash all...and see what happens.
If that doesn't work, install the new cameras.

...cameras work the same since putting the new ones back in. It opens, but locks up with a black/grey screen. Was going to flash all.bat, but the usb is no dorked. It will charge, but it's not recognized by PC. Took apart and checked again. Same problem.
Maybe I messed something up with a bit of rubbing alcohol trying to clean things up?

This has nothing to do with your camera. Its just the factory image you flashed. Try flashing another image.
sent from my nex7

Could you provide a logcat and the output for the following command in adb?
cat /sys/kernel/debug/remoteproc/omap-rproc.1/trace1
I am having a similar issue wherein both the cameras wouldn't work. It's a broken device that I have bought for development.

Sensors issue (acc., pros., gyro., lux). Android 5.0.1

My devices setting: stock OS, stock kernel, latest twrp and chainfire rooted. Nothing else. I updated from Android 4.4.4 straight to 5.0.1 (5.0 skipped) with fastboot clean flash, data, cache wipe.
So, the story went like this. I read a book on Google Play Books in landscape, then I put my device into sleep mode by closing the magnet cover. I closed it in landscape mode and left it in landscape.
Later, when I wanted to use my device again and I opened the cover to wake my device, the display was stuck in landscape. I didn't lock the autorotation.
I downloaded the app "Sensor Kinetics-Innoventions" to make tests of my device's sensors, pretty every kind of sensors. Here are the results, I attach some screenshots showing that the sensors cannot be detected at all (no numbers indication changing around. If you don't understand what I mean, try out the app yourself).
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
See, even the lux sensor doesn't work. Now my screen brightness doesn't adjust to the surroundings even when "adaptive brightness" is switched on my device.
FYI, I did a clean update from KitKat 4.4.4 to 5.0.1 skipping 5.0 using fastboot and official from factory image extracted system.img, boot.img, etc., wiped data and this kind of bug is what I encounter.
Normally, when the sensors are working, the app would show something like this (after reboot it fixed the issue, but only for a short time and I quickly made a screenshot):
The thing is, now, even a reboot won't fix the sensors issue. I am not in a mood to do all this flashing and setting up again, don't have that f*cking time. [emoji36]

Finally, I found a solution and temporary fix. The bug is actually caused by Google Now (I don't know which version though, maybe the lastest). I went to the Google Now "Ok Google voice recognition on every screen" and disabled it, rebootet and voila all sensors are working again. It has something to do with Google Nows constant voice recognition-ish thing. So this fix worked for me. Anyone wanted to know, here it is. Cheers and peace.

Nice to know

impressive!!! worked for me as well !

Secondary back camera

How to fix about secondary back camera turning off (disable).
Try to test with CIT mode (hw test) primary back camera turning on, but if i try to test vice camera (secondary back camera) its Will show primary camera, not secondary camera..
This bug always show on miuipro 10, rr rom, but with miuipro 9 its fixed.. Why??? Anyone know this issue???
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}

Don´t know what you mean. The second camera lens on the whyred does NOT deliver any image information and the image from this lens cannot be seen or displayed AFAIK. The second camera is only used in portrait mode to detect the outline of the object to be focussed on. The software is then generating a mask to limit the software blur effect to the areas OUTSIDE that main object.

Kusie said:
Don´t know what you mean. The second camera lens on the whyred does NOT deliver any image information and the image from this lens cannot be seen or displayed AFAIK. The second camera is only used in portrait mode to detect the outline of the object to be focussed on. The software is then generating a mask to limit the software blur effect to the areas OUTSIDE that main object.
Click to expand...
Click to collapse
You may try hw test mode (CIT) then You know i mean.. Secondary camera work or not..
Back Primary camera above side
Back Secondary camera below side

I have same problem..when I choose portrait mode (miui 9 also miui 10......recovery rom also fastboot rom)..it will show pop-up..can,t connect to camera. In CIT mode..twin back camera = fail. Is it hardware problem ?

Works fine for me in HW Test. All cams. Upon first check I had to select which cam app I want to use, selected stock cam.
Edit: just realized you're talking about Error on MIUI 10 and RR... I use MIUI 9.5.13.

Miuipro 8.5.10 -> normal
Miuipro 8.5.14 -> normal, i using right now.
Miuipro 8.6.21 miui 10 -> error
Miui 8.6.21 miui 10 -> error
Rom RR -> error
Miui pro 9.5.60 - normal

gumbung said:
Miuipro 8.5.10 -> normal
Miuipro 8.5.14 -> normal, i using right now.
Miuipro 8.6.21 miui 10 -> error
Miui 8.6.21 miui 10 -> error
Rom RR -> error
Miui pro 9.5.60 - normal
Click to expand...
Click to collapse
thx for this ...I'll try one of those roms to check my back camera..hopely just software..not hardware issues.

Moto Z play fingerprint scaner stoped working after oreo update

Hi there, im having this issue with my moto z play After updating to oreo ADDISON_OPN27.76-12-22 via adb the fingerprint scaner stoped working gradualy and even the option from security for the scaner is compeltly gone. This happens in a few weeks, after the update the scaner worked fine, with a few glithces like not recon the print or showing "the fingerprint scaner hardware is unabailable".
So what i try so far, reflashing the modem, reflashing the whole thing to oreo, safe mode for some stupid reason make it work but didnt last, I try instaling a 3rd party program to see it make the scaner visible for the system, and it worked but didnt last either. So im pretty sure that is a software problem, is not hardware related.
I google it and saw people with the same problem but with no solution (lenovo forums make me sick how they talk to clients like they where dumbass, ugggg).
My last shoot is to downgrade to 7.1, if I have to but I like oreo and besides from this problem, works like a charm .
If anyone has any idea how to make this work I'll apreciate all the help I can get. Thank you very much for reading me
PD: Im adding some pics of the system not showing the fingerprint option.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}

Looking in at this. I normally don't trust fingerprints as my old V570 liked to lock me out . I just yesterday RSDlited a Nov '17 ROM and let it ota itself up to 76-12-22 which is 8.0 Apr 1 . I am rooted via temporary TWRP ( thanks @jceballos fastboot boot nameoftwrptoflash ) and then did @rafikowy 's procedure.
https://forum.xda-developers.com/moto-z-play/how-to/guide-how-to-magisk-root-xposed-oreo-8-t3743273
I just set it up settings/security&Location/Fingerprint and set it up with fingerprint plus pattern. It took about 20 fingerprint presses before it was happy.
- I rebooted and first reboot stuck, second okay, no sound for Moto animation but i think that's a known prob, did a bunch of subsequent reboots and fast reboots, test blank scren, start screen, but all seems well.
- if you used exposed that might do something - I have no experience with exposed so always blame everything with it
- but I will leave this in and see if anything changes, but I normally leave my phone on 24/7 with DND on 11P to 8A.

KrisM22 said:
Looking in at this. I normally don't trust fingerprints as my old V570 liked to lock me out . I just yesterday RSDlited a Nov '17 ROM and let it ota itself up to 76-12-22 which is 8.0 Apr 1 . I am rooted via temporary TWRP ( thanks @jceballos fastboot boot nameoftwrptoflash ) and then did @rafikowy 's procedure.
https://forum.xda-developers.com/moto-z-play/how-to/guide-how-to-magisk-root-xposed-oreo-8-t3743273
I just set it up settings/security&Location/Fingerprint and set it up with fingerprint plus pattern. It took about 20 fingerprint presses before it was happy.
- I rebooted and first reboot stuck, second okay, no sound for Moto animation but i think that's a known prob, did a bunch of subsequent reboots and fast reboots, test blank scren, start screen, but all seems well.
- if you used exposed that might do something - I have no experience with exposed so always blame everything with it
- but I will leave this in and see if anything changes, but I normally leave my phone on 24/7 with DND on 11P to 8A.
Click to expand...
Click to collapse
This still works fine for me...

Fingerprint sensor does not work with unlocked bootloader

Having some issues while trying to root my 7T, I followed the guide here and everything seemed to work perfectly until I tried adding a fingerprint, at which point I was met with this message. It comes up straight away before I can even attempt to press the fingerprint sensor.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
I thought maybe I did something wrong and went back to stock, but I still encountered the issue. I then re-locked the bootloader and the fingerprint sensor became fully functional again. I've tried to search for solutions but I can't find other people experiencing this on the 7T.
I've also tried using a different OS, I went with MSM Xtended v12.0 which allows the fingerprint screen to open but it won't actually register any touches at all.
I've seen mention of a fix to the error relating to persist.img on other Oneplus phones but I'm unsure if this would apply to me seeing as the sensor works perfectly with a locked bootloader, basically I'm stuck at this point and would appreciate any advice

I have an unlocked bootloader and have no issues with my sensor. TMobile converted to International.
Revert to stock and try again.

jcotterman said:
I have an unlocked bootloader and have no issues with my sensor. TMobile converted to International.
Revert to stock and try again.
Click to expand...
Click to collapse
Yeah it seems to be working perfectly for everybody else on this device which is why I'm so confused.
I've gone from MSM Extended back to stock OOS 10.0.8 (HD65BA) and I still get the same error that's in the OP, I've now re-locked the bootloader and it's back to working again

RainingTerror said:
Yeah it seems to be working perfectly for everybody else on this device which is why I'm so confused.
I've gone from MSM Extended back to stock OOS 10.0.8 (HD65BA) and I still get the same error that's in the OP, I've now re-locked the bootloader and it's back to working again
Click to expand...
Click to collapse
It can be that something in /persist is broken. It happened to several others too but mostly it is a user error. This message pops up if the fingerprint sensor calibration data is missing or broken. You can try this guide to try to fix it (unless you have a persist.img backup which you can use): https://forum.xda-developers.com/on...de-fix-persist-img-loss-finger-print-t4125909
Keep in mind that the MSM tool doesn't touch /persist so using it isn't going to fix the issue if it due to /persist. But first try to unlock your bootloader again and see if this error pops up again. Maybe it fixed itself