My Z Ultra (C6833) was running stock Lollipop, with stock locked boot loader. I.e. the phone was completely stock.
I somehow managed to crack the bottom corner of the screen, which rendered the digitiser useless. I replaced the LCD/digitiser assembly, and have had nothing but problems since. First of all, since installing the new LCD/digitiser, the battery was idling at ~60 degrees, which was killing battery life and made the phone unusable. At this point, I unlocked the bootloader and flashed CyanogenMod CM11. CM11 solved the battery issue straight away (normal idling temperatures and excellent battery life). However, at this point neither of the cameras worked (black screen on opening any camera-using app). The app's controls were functional, but the app would eventually freeze with one of the well-known 'camera not available' etc. errors.
I figured that I may have accidentally left one of the camera's PCB connectors unattached, so reopened the phone to confirm. I downloaded a system profiler app, which clearly showed that both cameras are connected. Given the known camera-related issues with CM11, I figured I'd try another custom ROM. I flashed Resurrection Remix 5.5.9 this morning, which again worked beautifully, but the issues with the camera remained.
My last attempt was to flash stock 5.0.x Sony Android back onto the phone, and then re-lock the bootloader. Again, this whole process worked as planned, but the cameras are still non-functional. Given that the system profiler sees/lists in detail each of the cameras, I'm on the belief that the flex cables/PCB connectors are intact, as the camera modules themselves are communicating with the motherboard.
This is my first foray into custom ROMs and flashing, so please excuse my ignorance. Are there separate drivers for each of the modules, like you'd expect on a computer, or are the drivers combined with the ROM? I.e. could the camera module drivers have been corrupted in some way? All the evidence suggests that there's a software/firmware issue here, not a hardware one.
Given that camera-related issues are common for this phone and custom ROMs, I've been through just about every forum post/video/HOW-TO guide on the matter, so I'm afraid the solution won't be as simple as "clear the camera app's cache and restart the phone in safe mode"
Any input would be great!
Thanks
Does anyone have any ideas? I feel like I've exhausted the software/ROM side of this investigation, so am considering transplanting a motherboard from a second Ultra to try and fix this issue once and for all.
Have you tried to flash a stock ROM and run Sony's diagnostic test?
If that doesn't work its definitely hardware related.
Related
Hi there !
Tablet was pure stock , not even rooted when suddenly I couldn't start camera. It would say something that would translate to english like that " Error: camera is not available " or " Error: camera is not connected" .
I already tried:
- Using OTA to update to 4.2.2
- Flashing 4.2.2 using flash tool
- Unlocking bootloader and flashing P.A.C ROM.
- Wiping cache/dalvik cache/ fixing permissions/ wiping everything
- Downgrading to 4.1.1 original Japanese FTF.
- Rooting it and installing DOOMkernel
Nothing helped, still same error, which plaguages nearly every xperia phone/tablet...
I seem to havethe same problem
I have the exact same problem as your tablet, and mine is the 16 gb wifi model (Unlocked, rooted), The camera stooped working a few days ago, while i was running CM11, i assumed it was Kit kat, but the camera was working fine up until it randomly stooped working, so i reverted back to stock 4.2.2 (Flashed the SGP311FR 10.3.1.C.0.136 via Flashtool) and the problem is still there.
Im praying that it isnt hardware damage, due to the roms ive been using, and hope that its definitely software related. Im going to try ubuntu touch now, to see if a completely different os will make it work.
Do not worry guys. I had the exact same problem a few months ago with my SGP321. I tried all the things that you have mentioned above and still did not manage to get the camera working. You will have to be a bit adventurous to solve this issue. It involves opening the back panel of the tablet. There is an official teardown video somewhere on the Sony website which will give you an idea how to open it.
There is a very thin cable that connects the camera on the mainboard. It has probably gone loose. I had dropped my Tab a few times so maybe it must have become loose. Upon opening the back panel I saw that the cable was a bit loose. So i just snapped it back in place and voila the camera turned on. The only headache is that the back panel does not 'feel' waterproof anymore because it was opened. But i managed to glue it back again and since 3-4 months there have been no issues. Hope this helps! :good:
It worked
Thanks aashayjardosh
its quite a easy fix, the camera cable was not clipped in, so it must of fell out due to force (dropped, or thrown). i can say, im quite happy, not only did i fix my tablets camera, but i got to see the insides for myself , for now, i wont be dipping this thing into water any time soon, not untill i get some propper water resistant glue, and properly seal it.
To keep things simple, I had a cracked screen on the Ultra which was replaced last week. However now the phone screen is slow and unresponsive after about a minute of use (fast & like new after right turning on however).
Ive tried the mod tweak found here http://forum.xda-developers.com/showthread.php?t=2522657
As well as the thermal screen calibration here http://forum.xda-developers.com/showthread.php?t=2470070
There is no change with either mode. Cleaning with alcohol only works for a few minutes, and yes Ive removed the ASF for no change.
It should be noted that when booted at first minute or two, the touch inferface is quick and brilliant. After a minute or so it gets slower and remains so. Typing a text is a gruelling affair at that point,
Ran 4.3 android and updated to 4.4.4 and also no change in performance.
Does anyone have any ideas/ tips or pointers?
HELP!?!
An app with a memory leak?
Looks quite normal. RAM 1.1GB used; 600MB free.
Unless thats not what were talking about?
EDIT: might be up to something. using advanced kill on Go taskmanager EX and its seemed to do improve the situation in the short term. Will keep testing
Well got about that far thus far. The advanced kill works sometimes, but none of the apps look out of whack (from my basic knowledge anyhow)
Any help/ links in diagnosing a memory leak would be very appreciated.
Don't suppose you've got the Google now launcher? I had to uninstall as they introduced a memory leak in the last update.
Un updated it just in case.
Its tough as even watchdog lite isint detecting much. com.google.android.gms:snet at startup took 22% CPu but otherwise its steady.
Grr jezz I even did a factory reset to 4.4.4 and its still there. Would trying a custom rom help?
Well as an update manage to completely wipe and reinstall the OS. No change in performance however
Does anyone know if a faulty screen install could be to blame for this?
icehawk223 said:
Well as an update manage to completely wipe and reinstall the OS. No change in performance however
Does anyone know if a faulty screen install could be to blame for this?
Click to expand...
Click to collapse
Could well be, but i find it strange that it acts normal again after a reboot? That alone indicates that it's something wrong with the software. I still hold a finger on a process gone wild. Do you have Recovery installed? If yes, re-flash the ROM or flash something else and see if that solves it. I would personally flash a stock ROM and flash it with Flashtool so you don't have to root or void any warranties, and it'll be the simplest thing to do in case the screen is still acting weird after flash, and you want to get it checked out again (since it most certainly will be a hardware issue at that point).
So, fire up Flashtool, download a complete stock ROM (TFT), flash it, test it. Is it working fine now? Sweet. Keep using the ROM. Is it still the same thing? Contact the repair center again and tell them what's up and please do tell them that you've already done a factory reset, since that's the first thing they'll do themselves. Do not tell them about Flashtool or any other hacks or tweaks. They'll probably blame you if they think that you're an XDA user. "Oh, so you've been playing with it, and you bricked it and wanna fix it for free, bla bla".
Ask if they can open the device again and check that everything is fine and that you haven't received a faulty panel.
Ive actually did a complete tft flash of the original xperia ultra software. No change whatsoever vs previous state.
Im increasingly suspecting a hardware issue. Could it be a poorly plugged in cable? Its random chugging/ smooth response is completely confusing...
icehawk223 said:
Ive actually did a complete tft flash of the original xperia ultra software. No change whatsoever vs previous state.
Im increasingly suspecting a hardware issue. Could it be a poorly plugged in cable? Its random chugging/ smooth response is completely confusing...
Click to expand...
Click to collapse
Did you flash the exact same FTF that you've always used, or did you flash one from a different region? I would try the GPe ROM if i were you, just to be sure, but don't bother doing it if you're not rooted and ready to flash. Yes it can easily be a hardware issue, and you should probably contact Sony or your nearest service center.
As an update I tried installing a fresh tft flash of a different build but same issue.
Notably noticed that the notification light on the screen is not working at all, so currently looks like a hardware issue. Will keep updated for reference & visit a repair centre
A few days ago I noticed that the camera on my Nexus 9 stopped working (think this may have started after installing 5.1.1 but really don't use my camera much so I can't ignore the possibility the error started prior to upgrading). I would go to open the camera app and it would hang for a long time without ever progressing to the actual optical image. At some point the icon for the camera disappeared from my home screen and app drawer. I tried a few things to try and get the camera working again: 1) force close, clear cache/data, uninstall updates, reinstall updates and no change, 2) install alternate camera apps and use other apps to access the camera, but neither of them could access the camera, 3) turn off trusted faces and any other apps I could think of that would be accessing the camera but no progress, 4) completely wiped my device and reinstalled the 5.1.1 factory image from scratch and the same problems remained, 5) completely wiped again and installed latest Dirty Unicorns ROM and the camera wouldn't launch from here either (side note - performance noticeably improved otherwise and will be sticking around as daily driver), and 6) wiped and tried latest weekly release of DU to no avail.
I haven't yet flashed back to 5.0.2 because at this point I don't think it'll do anything and I wanted to consult the brain trust here before driving myself crazy or cracking open the casing to examine the hardware (no drops or impact to give reason to believe at fault).
Has anyone else experienced this problem or anything similar? I've done a bunch of searching but haven't seen other posts addressing this issue. There are posts about the Nexus 5 having some issues when other apps try to access the camera, but those posts also indicated the problem was cured by a reboot.
Tldr: cannot access camera and don't really know why.
i would not suggest opening it up to find out yourself. the camera is actually taped to the back of the case and there's a good chance you'll just pull it out and have to take it all apart to put it back in. i recommend just contacting google about it and getting a replacement, honestly. it sounds like it's probably a hardware issue, and it doesn't sound like it's something you're at fault for. if google doesn't help you then go to htc, they most likely will.
Update:
I went through HTC with a warranty repair. I was a little nervous as I did open the back in an attempt to reseat the camera connection and I left some visual signs of access. Also, I wasn't sure whether they would care whether (or would know if) the bootloader had been unlocked. I did restore completely to stock and re-lock prior to shipping to HTC.
Basically, everything went more smoothly than I could have imagined. I told the warranty rep on the phone about the problem and I got the impression they've had a decent number of repair requests triggered by recent updates. With very few questions asked, I was given shipping label on their dime and a claim number. I packed up my tablet, sent it in and got a new (refurbished? - it wasn't shipping in retail packaging, just the plastic wrapping around the front and back, but it looks untouched) tablet back within a few days. Again, I doubt they even looked at the tablet before sending out the new one.
Kudos to HTC for standing behind their product! I'll uphold my end of the implicit bargain and give them internet recognition in exchange for a painless warranty process.
Hi.
I just got my hands on a new Xperia Z3 Tablet Compact, and started to unlocking the first thing I did (of course!). I tried do back up the TA-partition, but run into some problem so I dropped that (so my DRM-keys are gone now). I used rootkernel v5.0 RC1 to repack the kernel from MM firmware for my tablet (23.5.A.0.570_R2D_Nordic Generic), with RIC off, TWRP and DRM-fix applied. Everything works great, except for my camera.
It seems that users with CM12.x have the same kind of problem i experience, no focus and mostly no change of exposure. And it don't take any pictures at all with it. When pushing the button, it seems that it tries to focus. That's it.
Thread with the CM12.x problem; http://forum.xda-developers.com/z3-...era-issues-using-cyanogenmod-12-cm12-t3070886
I can hear the camera when booting up, it makes some noise at the boot animation.
Anyone else experienced this kind of problem, and maybe have any solution for it?
-- Mike
Good day everyone, as the title says already changed battery, have read that after oreo update there's some kind of bug that is affecting battery, when I get into recovery mode there are no crashes so I'm guessing this is software related, already did factory reset and wiped cache. Anyone knows if this bug is real and how to fix it? Maybe flashing custom rom? Thanks a lot
I have the feeling that there is nothing to do with the oreo update. It's just coincidence. The crashing may occurred by an overworking function (as an example, while you are talking on the phone and searching sth on the internet or Facebook plus many background apps). This makes sense why you have no problems while you're in safe mode.
I also believe that except for the erratic batteries (GV30) some models have defective motherboards.
At my occasion, I got my phone back after random crashes from the service and they changed both battery and motherboard.
But, you always can try a custom rom!
In fact it worked for 2 days when changed battery, after that random crashes, maybe something to do with the new battery, its a gv one