Hey.
Well, on android 6 my gyro/accelerometer is working within reason (needs recalibration from time to time). When I install N7 rom (official or custom, does not matter) it is not showing anything (tested with sensor test app from store). Any clues? Tries safe mode, nothing, naturally wiped everything but the system, nothing. Probably HW defect but since that requires complete board replacement... i guess sticking to andro 6 will do.
Still, strange that it's working on version 6 and not on version 7.
Tx.
Sounds like a HW issue for sure.
Well, gave it a good (really good) whack over the knee, shattered the back glass, but, ever since all sensors back online, everything working, camera OIS is OK, all roms are fine... screen rotating on every version. No idea what that shock did, perhaps I shall, when I'll be replacing back cover, again, re-heat the gyro sensor connectors, but, even though it was much barbaric solution, done in even much more anger, it panned out (for now).
Related
Hello all... Well, I actually dropped my g-tab this afternoon and was very releived to find that all was working afterward. I dropped it onto a carpeted office floor (office carpet).... so I thought...
Then tonight, I went into the camera app and found that the camera lens must have been jarred by the fall, and is no longer centered in the little circle opening. Seems to be working fine, just offset and not capturing a full picture as it should.
I looked through the tablet disassembly thread, but it didn't really get to the camera part.
I guess I looking for advise and reccomendations on what I should do. Should I open it up and try to fix it myself (if it shifted up... I should be able to shift it back....right?????), or should I re-flash it to stock and try to get an exchange?
What do you think?
Thanks,
John
You'll probably need to go farther than I did, with disassembly. Not just taking off the back, but also removing the mainboard to get to the camera. You might even need to remove the LCD panel, but not certain.
Thanks Roebeet. I'm kinda leery about doing this while I'm still within my 30 day Sears return/exchange window.
I've now pretty much resigned myself to backing up what I have on TNTLite 2.2, restoring my CWM backup from right after the 1st OTA update, and exchanging it for another g-tab...
John
Do you really think sear's sales rep would really check/know what rom you're sporting or check for root?
I'm going today to replace my g tab, I noticed my camera is inverted or mounted wrong. I switch to portrait mode in fring and my image is 180 degrees off, yahoo 90 degrees on lanscape. Running TnT lite 3.1... I'm assuming it's a hardware issue but I'm not too sure.
But I wont be wasting time reverting back to stock.
mnm101 said:
I noticed my camera is inverted or mounted wrong. I switch to portrait mode in fring and my image is 180 degrees off, yahoo 90 degrees on lanscape. Running TnT lite 3.1... I'm assuming it's a hardware issue but I'm not too sure.
Click to expand...
Click to collapse
Mine has the same issue. I don't think it's hardware related as it's fine in the camera app.
Just noticed it wasn't working. I've flashed back to rooted stock and tried several apps with nothing working. I can't say if it ever worked as I never use it. Has anyone tested this to see what could be the issue? Does it work on a clean phone, unrooted stock original? Are we somehow messing the magnetometer up with flashing?
Bump. Anyone tried their compass even?
Wouldnt rely on it. Ive had the phone sitting on a table with the compass pointing North, closed the app and reopened and it was way off. Closed and opened again and it was pointing a different direction.
So your compass is broke as well. There are phones where this works. It's nice for apps like google skymaps. Question is does it come broke or does rooting/unlocking/flashing somehow mess it up.
I have yet to see a phone where the compass works consistently. Due to the fact that some countries restrict the use of very sensitive magnetometers I doubt we will ever have very reliable ones in cell phones.
Perhaps but this is an advertised feature of a US based phone. We have every right to expect it to function. The question is does it function at all even on new in bow devices. Some youtube videos show it working bit it's not clear if those are i9300s or i535s. It could also just be an unreliable device hitting on some and being broke on others.
So using the sensor test (*#0*#) I was able to see my y axis sensor is very low. It goes above the threshold when the top of the phone is oriented north. The device must be calibrated to start and periodically. It also loses direction if turned up as you would for google skymaps. This makes the app useless. Other devices do not have this problem. I believe I have a defective sensor but also that samsung drivers are shotty. Can anyone else look at their readings and report?
This is probably related to the crap GPS as well. I believe the issue can be fixed in the kernel too bad we don't have many devs that work on the kernels.
Where in the hell is the compass?
Android 4 Life
The compass is a built in piece of hardware that you need an app to see. Search for compass in the play store. Any one should work.
On a sidenote, a Samsung rep checked two of their devices and found it working. One was a vzw on 4.04 and the other was on 4.1. I tried to get him to send me the 4.1 rom to test on but he couldn't.
This may be a sporadic problem inherent in only some devices.
Had vzw ship me a new one but before I returned the old one I flashed it back via odin and low and behold, the compass came back. Even on a stock rom that was slightly modified it wasn't happening. After odin, I was able to root, unlock and flash cwm and keep it running. Once I flashed any rom, the compass was dead but I could flash back to a backup of the stock unmodified rom and it worked. So it's a software issue and I'm going to return the warranty replacement.
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.
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.
After i replaced the amoled display everything seemed to be normal. But then after some month i had to unscrew my phone to replace the battery and install new camera replacement. And when i was sealing phone i missed a bit my screw and kinda broke the signal cable (long one, it was flattened a bit).
And then after that i promptly noticed that my wifi range plummeted tremendously. Seriously, router was not seen at all just 10m off it! (still worked thought)
And not long after that(maybe it was since the wifi issue arose, maybe it was a bit later) i also noticed that GPS connection is missing too. I checked all the apps to make sure, gps test showed absolutely nothing.
I checked my antennae inside the phone and it looks like ok. I even flashed my phone to miroom 20.3.26 but still issue is there.
I'm running out of suspects by this moment and i really need your help.
I'm starting to realise that it may be a complex mobo repair
Amrch787 said:
After i replaced the amoled display everything seemed to be normal. But then after some month i had to unscrew my phone to replace the battery and install new camera replacement. And when i was sealing phone i missed a bit my screw and kinda broke the signal cable (long one, it was flattened a bit).
And then after that i promptly noticed that my wifi range plummeted tremendously. Seriously, router was not seen at all just 10m off it! (still worked thought)
And not long after that(maybe it was since the wifi issue arose, maybe it was a bit later) i also noticed that GPS connection is missing too. I checked all the apps to make sure, gps test showed absolutely nothing.
I checked my antennae inside the phone and it looks like ok. I even flashed my phone to miroom 20.3.26 but still issue is there.
I'm running out of suspects by this moment and i really need your help.
I'm starting to realise that it may be a complex mobo repair
Click to expand...
Click to collapse
I would start with reflashing original stock ROM with MiFlash tool. If the issue persists on stock ROM with locked bootloader, then you should go for repair