I have a problem with the OPO, I have it since 2 years and it never had problems, unfortunately in January it was accidentally crushed and it bended slightly at the top. Of course touchscreen, frame and back cover got destroyed. I replaced the components hoping the motherboard was not compromised, once changed the components it seemed all right, the only problem is when shooting photos, after a few seconds the phone freezes and reboot the system. I tried changing also the camera module but the issue still remains. Autofocus seems not working too. Obviously I formatted and made a clean install after changing the components, i had the issue before and after the format. Which could be the cause of this issue?
Thanks
ponzaro said:
I have a problem with the OPO, I have it since 2 years and it never had problems, unfortunately in January it was accidentally crushed and it bended slightly at the top. Of course touchscreen, frame and back cover got destroyed. I replaced the components hoping the motherboard was not compromised, once changed the components it seemed all right, the only problem is when shooting photos, after a few seconds the phone freezes and reboot the system. I tried changing also the camera module but the issue still remains. Autofocus seems not working too. Obviously I formatted and made a clean install after changing the components, i had the issue before and after the format. Which could be the cause of this issue?
Thanks
Click to expand...
Click to collapse
It seems you have hardware problem
FSadino said:
It seems you have hardware problem
Click to expand...
Click to collapse
I've already tried to change the camera module but the problem is still there. What can it be? The mainboard?
Thanks
ponzaro said:
I've already tried to change the camera module but the problem is still there. What can it be? The mainboard?
Thanks
Click to expand...
Click to collapse
Its difficult to achieve a conclusion but I think the main board is the reason
Related
Hi!
I have recently purchased a camera replacement unit from ebay since the original one got damaged after a motorbike crash. I am sure that I have connected it properly and have not damaged it during the procedure. Still, once I open the camera app, it either crashes or and error message pops up stating "cannot connect to the camera"(I have tried using other apps, but they also did not work). Have someone else encountered some similar issues once they have replaced their camera? Can you suggest some possible workout for the situation?
Thanks.
I have replaced mine, the module was stucked to the frame and when pulled off, would expose the back of the board,would interfere in direct contact, I tried to cover it or use tape, worked now an then,
I ended up buying another camera, attached it an it worked.
I didn't buy a genuine one.
republicano said:
I have replaced mine, the module was stucked to the frame and when pulled off, would expose the back of the board,would interfere in direct contact, I tried to cover it or use tape, worked now an then,
I ended up buying another camera, attached it an it worked.
I didn't buy a genuine one.
Click to expand...
Click to collapse
Mine is also not a genuine one but still I guess that these cameras should at least work ... Could it be that the camera is damaged (probably from the transportation although the package was well protected) so badly that it won't even start?
P.S. DId you do anything except from attaching the new camera (wiping cache, installing some additional software, etc) ?
ivan.panchev said:
Mine is also not a genuine one but still I guess that these cameras should at least work ... Could it be that the camera is damaged (probably from the transportation although the package was well protected) so badly that it won't even start?
P.S. DId you do anything except from attaching the new camera (wiping cache, installing some additional software, etc) ?
Click to expand...
Click to collapse
I think I may have flashed a stock ROM, I think I tried KitKat first then gone up to lollipop, the camera ribbon cable needed a bend so the connection would fit properly
On rooted Developer Edition Ultra:
Is there any additional procedure needed after replacing the rear camera module? The phone has random camera busy/restart errors. Attempting to isolate apps via SafeMode was inconclusive. So, I decided to disassemble the phone and re-seat the camera ribbon cable - after reassembling, the camera works for a day or two - then the error appears for a while.
Thinking that it might be a failure of a camera component itself I replaced the module with a new one (bought from eBay) yesterday and when reassembled/rebooted - the new camera did not appear. I reinstalled the original camera which is currently working.
FYI - all ribbon cables are aligned, clips tight etc.
When I have some time I will reinstall new camera again and reflash with 4.4. Does anyone know if a new module needs to be 'initialzed'? My assumption was that installing the like component would simply 'work'.
Here is my experience when my rear camera started failing. The cause was from a drop, landed face down with a case, no visible damage, not a single scratch. After a few days, the camera start failing to initialize. I can get it to work by squeezing on the back case just right. Opened it up and started playing with the ribbon, taking the entire motherboard out, etc. Ended up replacing the camera and still the same. The cause I believe was a hairline fracture to the motherboard caused by the drop. I was still under warranty and Motorola replaced my phone no questions asked. I used the website so I never even spoke to anyone. So, that was my experience with this issue.
Sent from my iPad using Crapatalk
Thanks Johnny - that sounds familiar - my XT1080 took a hard fall once. Camera problems started after but I always attributed the issue to the move from 4.2 to 4.4. Camera is working well right now though I do have to restart the phone every day or so. Before I used to have to press on the phone back below the camera. Your symptoms are almost identical to mine.
The issue I had after replacing the camera was that the rear facing camera did not appear in the app after reboot - only the front facing camera. When you tried the new camera was it recognized immediately by the phone?
This Ultra D.E. is my 'daily driver' it does everything I need - it's out of warranty and sending it to MOTO for repair will cost $183. If I don't sort it out with another camera, I will assume that the motherboard is at fault (that of course was my next assumption). Thanks for confirming the problem.
I'll post a follow-up as soon as I either fix it or send it to MOTO.
It should just pick it up. There usually ins't anything you need to do. My guess is that there is some type of micro fracture, and when you installed the new camera it affected it just right, not letting android detect it. Try it again. Either that, or the camera you received was DOA, or has its own problems with the cable etc... hard to tell.
Try taking a good close look at the motherboard, maybe with a magnifying glass, see if you notice any small lines or breaks.
Hi, I have a galaxy s6 and its back button is pressing itself, without me touching it, closing apps and making it unusable. Using warranty isnt an option as it was bought abroad.
What are my options? Is this necessarily a hardware problem or could it be software related?
me too have this problem
vitalianoleone said:
me too have this problem
Click to expand...
Click to collapse
I had similar then found that the animations (in developer) were set to 0.25, reset them to 1, used rebooted a few times and now its OK. Could be coincidence but tried reboot, clearing cache etc before the Animation setting?? Weird but may be worth trying.
gmlogan said:
I had similar then found that the animations (in developer) were set to 0.25, reset them to 1, used rebooted a few times and now its OK. Could be coincidence but tried reboot, clearing cache etc before the Animation setting?? Weird but may be worth trying.
Click to expand...
Click to collapse
ill try, but i dont think itll help much...
dgershko said:
ill try, but i dont think itll help much...
Click to expand...
Click to collapse
my phone is already set to animation 1s
I change launcher and now the problem seems to be less frequent (I install nova at the place of next launcher)
I think that the problem maybe depend by some app not perfectly compatible with lollipop 5.1.1.
I had this problem on my S6 and when I googled it, it seemed to be a recurring issue on Samsung phones. Poor insulation causes the radio to leak into and trigger the captive buttons in weak signal areas. What eventually fixed it for me was replacing my tempered glass screen protector with another one, as non-unrelated as it sounds.
keijikage said:
it seemed to be a recurring issue on Samsung phones. Poor insulation causes the radio to leak into and trigger the captive buttons in weak signal areas.
Click to expand...
Click to collapse
Mine never made that, even in poor/nonexistent areas... I believe that has massively to do with the production quality of every particular product. Some of them might be a little bit better fabricated than others.
I had this problem. Luckily I was on warranty and just switched it out. I would try factory reset tbh, that's the only thing I didn't try
Dear all,
A few days ago, my N5's camera stopped working and none of the usual solutions (reboot, clean data and cache of camera app, even complete wipe and change of ROM) did anything to fix the problem. So I went on ebay, and bought a replacement back camera, fitted it and all was well...for a day!!! It looks like after just one day (and nearly no use at all) the new camera has already stopped working. Is anyone aware of what may be causing it, and of a way to fix it? or is it time for a new phone?
Thanks for your help!!
Is it possible the camera connction on the motherboard is a bit flaky?
audit13 said:
Is it possible the camera connction on the motherboard is a bit flaky?
Click to expand...
Click to collapse
Thanks for your reply. I thought that too after the second camera went wrong. I re-opened the phone and checked the connection, and from what I can see it seems quite solid. I am not sure what could possibly be going wrong that causing 2 camera modules to go bad in quick succession though. While the rest of the phone works perfectly.
Maybe it's just coincidence. I guess you could try a third camera to see what happens.
Can't connect to camera
My camera quit working the day I updated to 6.0.1
At first it would work for a few hours after a fresh boot. Now it won't work at all. I replaced the camera module with a working one and it worked for a few hours then died. Now all I get is "can't connect to camera". I'm convinced its related to the marshmallow update.
Safe mode doesn't help. Factory reset doesn't help. Third party apps still let me use the front camera but the rear is dead. I think I've reached the end of the road buying nexus devices and beta testing OS releases.
Maybe it because of your sd card
dixie600mhz said:
My camera quit working the day I updated to 6.0.1
At first it would work for a few hours after a fresh boot. Now it won't work at all. I replaced the camera module with a working one and it worked for a few hours then died. Now all I get is "can't connect to camera". I'm convinced its related to the marshmallow update.
Safe mode doesn't help. Factory reset doesn't help. Third party apps still let me use the front camera but the rear is dead. I think I've reached the end of the road buying nexus devices and beta testing OS releases.
Click to expand...
Click to collapse
Initially I thought this may be a normal issue of age of the phone, but the fact that a few of us are bumping into this so shortly after the marshmallow upgrade makes me think maybe the 2 things are related.
I suppose I could try and install a lollipop rom and buy yet another camera module.
The only component that should face problems in a persons lifetime would be the battery. It is a shame that companies and people treat this stuff as disposable.
OP and others who cannot fix this through software, or a small hardware change, this must be a hardware issue. Something on the mainboard is messing with the camera. Others are running stock marshmallow fine, to rule out any software issues, wipe all and flash new (manually wiping and flashing each partition from fastboot would be best). Report back.
wangdaning said:
The only component that should face problems in a persons lifetime would be the battery. It is a shame that companies and people treat this stuff as disposable.
OP and others who cannot fix this through software, or a small hardware change, this must be a hardware issue. Something on the mainboard is messing with the camera. Others are running stock marshmallow fine, to rule out any software issues, wipe all and flash new (manually wiping and flashing each partition from fastboot would be best). Report back.
Click to expand...
Click to collapse
Thanks for your reply. Done, but to no avail. Infact when you flash from fastboot the camera app is not even installed and the torch does not show up in the notification bar.
It is definitely a hardware issue, which is not resolved by simply replacing the camera module, as that seems to break again in a short amount of time. Not sure if I feel investing in a new mainboard and a new camera module.
Anyone experiencing ghost touches on the center part of the display? I thought I was just accidentally touching but it turns out there are ghost touches. It rarely happens and I still couldn't figure out the reason. Note: cleaning the screen of moisture didn't help.
ijuanp03 said:
Anyone experiencing ghost touches on the center part of the display? I thought I was just accidentally touching but it turns out there are ghost touches. It rarely happens and I still couldn't figure out the reason. Note: cleaning the screen of moisture didn't help.
Click to expand...
Click to collapse
Haven't noticed personally. Using a screen protector?
I removed the screen protector to check if is causing it but still the same. It happens rarely though.
ijuanp03 said:
I removed the screen protector to check if is causing it but still the same. It happens rarely though.
Click to expand...
Click to collapse
Hmm. It happens during use or in charging or ?.
Shadowthor said:
Hmm. It happens during use or in charging or ?.
Click to expand...
Click to collapse
During. When I'm just scrolling through my apps or even playing games. It doesn't matter if I am in a cold or warm environment. It even happens when I'm doing basically nothing - staring at my homescren and suddenly it opens the app located at the center.
To give you a better view, here's my homescreen. The ghost touch is located on Waze app but sometimes on Moto or even Settings app.
Try safe mode.
I would ditch Waze app and flipboard.
Try clearing the system cache.
See what's running in the background when it happens.
Use the factory diagnostic touch screen test to see if it may be hardware caused. Not sure how you access it it on that phone.
ijuanp03 said:
During. When I'm just scrolling through my apps or even playing games. It doesn't matter if I am in a cold or warm environment. It even happens when I'm doing basically nothing - staring at my homescren and suddenly it opens the app located at the center.
To give you a better view, here's my homescreen. The ghost touch is located on Waze app but sometimes on Moto or even Settings app.
Click to expand...
Click to collapse
Hmm that's weird. Did it happen recently? Did you install any new apps?
Hopefully it's not hardware related.
You can use cqa test to check the hardware. *#*#2486#*#*
Nahhh it's not related to any app. I may be wrong but it could be the software update from Motorola since I didn't encounter the issue when I first used the phone.
ijuanp03 said:
Nahhh it's not related to any app. I may be wrong but it could be the software update from Motorola since I didn't encounter the issue when I first used the phone.
Click to expand...
Click to collapse
A new update got pushed out?
Not entirely new. The latest software update RR31.Q2-12-14-7.
Shadowthor said:
A new update got pushed out?
Click to expand...
Click to collapse
ijuanp03 said:
Not entirely new. The latest software update RR31.Q2-12-14-7.
Click to expand...
Click to collapse
Oh that update. I have it but I don't currently see the ghosting issues you mentioned yet. Did you end up using the cqa test to check screen?
Shadowthor said:
Oh that update. I have it but I don't currently see the ghosting issues you mentioned yet. Did you end up using the cqa test to check screen?
Click to expand...
Click to collapse
Yah. All the standard testing done. My phone seems to work fine now after removing 1 sim while keeping the other. It must be affecting the internals when dual SIM is utilized which is a design flaw or was not tested properly.
ijuanp03 said:
Yah. All the standard testing done. My phone seems to work fine now after removing 1 sim while keeping the other. It must be affecting the internals when dual SIM is utilized which is a design flaw or was not tested properly.
Click to expand...
Click to collapse
Could be a blown sim card. Replace both and follow ESD protocol when handling them, always.
Handle like a stick of ram.
Excessive ESD exposure can cause random failures immediately or worse, days, weeks even years latter. These cards are dirt cheap but a delayed failure can cost you dearly...
ijuanp03 said:
Yah. All the standard testing done. My phone seems to work fine now after removing 1 sim while keeping the other. It must be affecting the internals when dual SIM is utilized which is a design flaw or was not tested properly.
Click to expand...
Click to collapse
Hmm weird. Haven't tested out dual Sim but it shouldn't cause this issue.
I have encountered at least 30 users reporting this problem in China. Including but not limited to many users from official forums.
https://mclub.lenovo.com.cn/forum-1567-1.html
https://mclub.lenovo.com.cn/thread-7814429-1-1.html
https://mclub.lenovo.com.cn/thread-7814577-1-1.html
https://mclub.lenovo.com.cn/thread-7814895-1-1.html
nullschool said:
I have encountered at least 30 users reporting this problem in China. Including but not limited to many users from official forums.
https://mclub.lenovo.com.cn/forum-1567-1.html
https://mclub.lenovo.com.cn/thread-7814429-1-1.html
https://mclub.lenovo.com.cn/thread-7814577-1-1.html
https://mclub.lenovo.com.cn/thread-7814895-1-1.html
Click to expand...
Click to collapse
And so I thought mine is an isolated case. Motorola is yet to confirm if this is hardware or software related.
ijuanp03 said:
Anyone experiencing ghost touches on the center part of the display? I thought I was just accidentally touching but it turns out there are ghost touches. It rarely happens and I still couldn't figure out the reason. Note: cleaning the screen of moisture didn't help.
Click to expand...
Click to collapse
Hello everyone!
I have this same problem here on my brazilian Moto G100 and in the same place almost in the center of the screen. After removing the screen protector, the problem is more difficult to happen, but it still happens rarely, requiring a cleaning of the screen for the problem to stop happening for a while.
I noticed that the problem happens several times when I leave the smartphone leaning against metallic surfaces or other electronic devices.
Is it necessary to use the warranty to replace this screen or can a firmware update solve this problem?
Regards!
I'm Chinese user.My device have this problem.Our forum many people reaction to this problem
I can confirm I have the same problem. I don't know if it's hardware or software yet
wow I haven't had any problem, but if you find any solution or coment from motorola sopport please post it