Hi, I've spent some time looking @ our camera since there is no evidence of sony breaking camera or not and people seem to be doing alot of guessing, some say DRM keys some say binaries causing issues etc. Enough of guessing and lets take a look at what really is going on.
This thread will look at both improving the camera & auto focus issue along with current AOSP errors
Our camera HW =
What our device currently supports: (to be filled in)
Yes Google is working on RAW camera support (We cannot enable it for our devices)
Apparently unlocking the bootloader breaks camera?????????
Build.prop modifications:
persist.camera.feature.cac (value = 1/0) (not sure what this does yet)
persist.camera.dumpimg (stores to data/img.jpg)
persist.camera.snapshot_raw (
persist.camera.preview_raw
persist.camera.zsl_raw
persist.camera.zsl_yuv
persist.camera.opt.livepic
persist.camera.zsl.interval
persist.camera.zsl.backlookcnt
persist.camera.zsl.queuedepth
persist.camera.snapshot.number
persist.denoise.process.plates
persist.camera.snap.format
persist.capture.burst.exposures
persist.debug.set.fixedfps
persist.debug.sf.showfps
persist.camera.thermal.mode
persist.camera.mem.usecache
persist.camera.longshot.save
persist.camera.dumpmetadata
pretty much self explanatory, but will give more indepth information later on these, what to set these values to and what they do...
Installed Carbon ROM which is pretty awesome but I came across errors in general and ones that are related to camera...
General Errors:-
Kernel:
SPKDRV supply cdc-vdd-spkdrv isn't defined
timeout while setting prog bit, ETMSR: 0x0
Cache ERP
ROM:
Missing binarys
Camera Errors:-
Kernel:
AVC
ROM:
Errors - IDD-API: IDD_SET_SDATA : SEND FAILED Socket 34 Errcode 2 (No such file or directory)(IMPORTANT ERROR)
Error - QCOM_SENSOR_HAL
LIBCAMERALIGHT - Sys Interface Error (this errors can be fixed by giving it write permission)
Error from Focus detector
LIBALS-SYSALS /dev/input/uevent8 (PERMISSIONS DENIED)(IMPORTANT ERROR)
CREDMGRLIB Send/Recieve socket failure Error!! (Important) (CREDMGR_RESULT_GENERIC_ERROR
Ckb create failed
Ckb is not ready
Note:
Camera Focus Distance = Infinite???? :s
Cam parameters before param fixup is called: focus-areas=(0,0,0,0,0)
Cam Parameters after param fixup is called: focus-areas=(-510,30,-398,230,1)
The above is only to identify the current errors with AOSP, when I have more free time and hopefully an upgraded PC I will be able to compile, diagnose and hopefully fix some of these...
I have a rough idea on what is going on with the camera now, will take alot of testing and patience thank you
1080p 60fps will be released soon after more testing....
1080p 60fps:
If it was like you think, why is the camera broken just by unlocking bootloader on a stock rom? Or is it not ?
Guys, it's simple.
The problem happens just because unlocking the bootloader will zero out the DRM partition.
Then, the focuser blob calls the internal DRM authentication that actually fails because of wrong keys... and that produces unability to start a server that is responsible of the communication with the actual focuser kernel driver.
That's all.
If anyone cracks the DRM binaries by Sony to change the reply, both X-Reality or Bravia as you want to call it, AND the focuser will work.
kholk said:
Guys, it's simple.
The problem happens just because unlocking the bootloader will zero out the DRM partition.
Then, the focuser blob calls the internal DRM authentication that actually fails because of wrong keys... and that produces unability to start a server that is responsible of the communication with the actual focuser kernel driver.
That's all.
If anyone cracks the DRM binaries by Sony to change the reply, both X-Reality or Bravia as you want to call it, AND the focuser will work.
Click to expand...
Click to collapse
Why do you know it's DRM? I would say it's just the binaries, not DRM
Sent from my Xperia Z1 using xda app-developers app
cocchiararo said:
If it was like you think, why is the camera broken just by unlocking bootloader on a stock rom? Or is it not ?
Click to expand...
Click to collapse
I was thinking about that, will test it too
kholk said:
Guys, it's simple.
The problem happens just because unlocking the bootloader will zero out the DRM partition.
Then, the focuser blob calls the internal DRM authentication that actually fails because of wrong keys... and that produces unability to start a server that is responsible of the communication with the actual focuser kernel driver.
That's all.
If anyone cracks the DRM binaries by Sony to change the reply, both X-Reality or Bravia as you want to call it, AND the focuser will work.
Click to expand...
Click to collapse
krabappel2548 said:
Why do you know it's DRM? I would say it's just the binaries, not DRM
Sent from my Xperia Z1 using xda app-developers app
Click to expand...
Click to collapse
@everyone this isnt a [letshaveaguesswithnoevidence] thread... Its a [dev] thread, dev posts which include debugging/evidence will be taken seriously.
Hope you guys reach a solution soon.
Good luck.
Sent from my C6903 using Tapatalk
i wouldn't say, that the camera issue is a binary problem.
i would say it is the DRM-partition ... BUT ... i was thinking about that issue and tried a lot ... ONE thing was to flash a rooted and deodexed STOCK rom on unlocked bootloader. cam wasn't working, but that was, what i expected ... then i recovered my TA-Partition and the bootloader, the rom was bootable after that (stock kernel with stock rom, just modified) but the cam was not working ... so the TA and BL recovery hasn't fixed the cam issue ...
don't know, what exactly is the problem with the cam, but i think we have to be more focused on that, because that is one reason, why people will not flash our roms and withot people trying our roms, the bug reports will not be very much ...
so if we will be able to get the camera working, there will be much more users testing our roms and kernels on their devices and we will get better feedback.
So i think the cam is the NUMBER ONE problem of our nice devices ....
I think your initiative is something to be praised here.Maybe if more devs pitched in, you could work together on this and at least come up with a few more ideas so we have a better understanding of what's actually going on (which is a start).
I'm sure that Sony would also follow your work and I'm sure they will release a fix sooner than later (it's their flagship). I was very dissapointed by this bootloader unlocking bug and I really hope this will get fixed because I for one love this phone (been using it for a month now).
I wish you good luck in this endevour! )
DJ_Synergy said:
then i recovered my TA-Partition and the bootloader, the rom was bootable after that (stock kernel with stock rom, just modified) but the cam was not working ... so the TA and BL recovery hasn't fixed the cam issue ...
Click to expand...
Click to collapse
I did this many times and always cam worked fine. Just wipe cam data after restoring TA. And of course your TA must be backuped BEFORE first unlocking.
cocchiararo said:
If it was like you think, why is the camera broken just by unlocking bootloader on a stock rom? Or is it not ?
Click to expand...
Click to collapse
Tested, it does not work with stock rom/stock kernel on unlocked bootloader... Interesting...
kholk said:
Guys, it's simple.
The problem happens just because unlocking the bootloader will zero out the DRM partition.
Then, the focuser blob calls the internal DRM authentication that actually fails because of wrong keys... and that produces unability to start a server that is responsible of the communication with the actual focuser kernel driver.
That's all.
If anyone cracks the DRM binaries by Sony to change the reply, both X-Reality or Bravia as you want to call it, AND the focuser will work.
Click to expand...
Click to collapse
You are correct, clearly you have checked this out earlier, it is the DRM keys which isnt allowing the camera to activate, its not like the camera focus is passing wrong values, the camera doesnt function at all on focus, hw focus detector error, credmanager, looks like credmgr wants the keys but isnt receiving them so doesnt activate bravia/imageproccessor...
Methods to get this working would be...
1. Crack DRM (Difficult, I wont attempt this)
2. Kexec (delewer has been working on it and he has taken it far, in talks with him, attempting to help him whenever I can)
3. Run AOSP on stock kernel... (Anyone attempted this? Not sure... Can it be done? Most likely... (wont benefit from custom kernel e.g. Overclocking undervolting etc etc))
Best option looks to be number 2, kexec
Edit: Further testing, Lets see if I can fool the device in thinking I already have the keys...
Shaky156 said:
Tested, it does not work with stock rom/stock kernel on unlocked bootloader... Interesting...
You are correct, clearly you have checked this out earlier, it is the DRM keys which isnt allowing the camera to activate, its not like the camera focus is passing wrong values, the camera doesnt function at all on focus, hw focus detector error, credmanager, looks like credmgr wants the keys but isnt receiving them so doesnt activate bravia/imageproccessor...
Methods to get this working would be...
1. Crack DRM (Difficult, I wont attempt this)
2. Kexec (delewer has been working on it and he has taken it far, in talks with him, attempting to help him whenever I can)
3. Run AOSP on stock kernel... (Anyone attempted this? Not sure... Can it be done? Most likely... (wont benefit from custom kernel e.g. Overclocking undervolting etc etc))
Best option looks to be number 2, kexec
Edit: Further testing, Lets see if I can fool the device in thinking I already have the keys...
Click to expand...
Click to collapse
Maybe we can plant a ta-dump on credmgr somehow? Maybe we can find the start-address where credmgr looks for TA, place the dump in ram und modify the address in the binary to point it there.
When the bootloader is unlocked, what is altered? Certain things stop working, like DRM content, I believe this is the main cause of the camera not working, I'm thinking is there a way to spoof the system, forcing it to believe that that specific part of the DRM (for the camera) is still intact, when the bootloader is unlocked? Perhaps if the app / program used to unlock the bootloader could be obtained and modified to allow the specific part of the unlocking to leave the camera intact ??? Just an idea.
Of course that would mean isolating it, which i can't see being easy.
Really bad on Sony's part for letting this happen, surely they would have tested it prior to releasing it ?
With that in mind it would seem that it was Sony's intention to have the camera not work if you unlocked the bootloader, really don't understand this approach.
Yes sony wanted to break camera, with all the stuff ive seen today contained within our devices... Breaking camera was no mistake by sony
4k wont happen unless Sony allow it, camera only passes 1080p, have to use specific yuv(Venus) format for 4k afaik, max fps available is 60 on both 720p & 1080p, no HFR(90. 120, 150fps mode available)
Will update OP with more information regarding what our cameras can support
Also i see the light at the end of the tunnel... Regarding kexec
Yeah, Kexec would be the workaround for that. The Keys would stay untouched cause of the old kernel and the new kernel will boot the system ... if the system then read the key, it will get correct values out of the partitions ... just in theory ...
So if we can get kexec to work, it may not break the camera and we have a good workaround for that ...
will try to help on kexec ... hopefully we can get it to work ...
---------- Post added at 11:37 AM ---------- Previous post was at 11:26 AM ----------
Desperanto86 said:
I did this many times and always cam worked fine. Just wipe cam data after restoring TA. And of course your TA must be backuped BEFORE first unlocking.
Click to expand...
Click to collapse
TA backup had been the first i have done so yeah, for sure BEFORE unlocking ...
haven't tried to wipe camdata so that was the fault ^^ ... will try it again
Just a thought... not sure if it is possible (since I'm not that familiar with embedded systems and such)..
but could it be possible that only certain parts of the TA-partition are restored when restoring the backup after unlocking, so the DRM-stuff is retained?
Guyz just want to know, camera will be back (from Sony or anothers) ??
kartal172 said:
Guyz just want to know, camera will be back (from Sony or anothers) ??
Click to expand...
Click to collapse
You really shouldn't be asking for this here. This issue is frustrating enough without having people asking for ETAs. If you want to help, pressure Sony online to give us an update on their status.
Sent from my K00C using XDA Premium HD app
cursordroid said:
You really shouldn't be asking for this here. This issue is frustrating enough without having people asking for ETAs. If you want to help, pressure Sony online to give us an update on their status.
Sent from my K00C using XDA Premium HD app
Click to expand...
Click to collapse
Just asking that is confirmed from Sony possible fix or any news?
kartal172 said:
Just asking that is confirmed from Sony possible fix or any news?
Click to expand...
Click to collapse
There is no confirmation. There is no news.
I have twitted them several times without answer
As above. Plus the advantages and disadvantages of unlocking z1 compact bootloader.
If you want to flash for example custom kernels you will need to unlock it. Some actions just require an unlocked BL.
Disadvantege is that you COULD have issues when sending it in for repair when you messed up the software.
But when you are careful and backup everything you can always restore it. You can also relock it if necessary (backup TA partition!)
I always unlock the bootloaders on my devices and never had any problems.
But its up to you.
I agree. It just depends on your goal.. If you just want a solid setup with trusty performance that you can use daily for a long time, and sync your emails, social sites, financial, etc., then you're probably best off leaving it alone. If you're into customization and trying new things, it's worth it. From what I've read, the only things you lose are the official support issues mentioned above, and some kind of camera functionality that I'm not real clear about. But, there's a lot of development for this phone, and the unofficial support here is likely better than any official support, and you can probably find a solution here for anything you lose.
Thank you so much for your responses .Though I dediced to unlock it anyway. I want to try other kernels .
I have UB, my answer is no, unlock bootloader when you want to try Android 6.0.
Well. For me I decided not to unlock. More than experimenting I need stable working phone, on all areas. Especially Wi-Fi. And I have not time to play every evening with flashing and reflashing.
Stock stuff is not that bad if tuned.
Android 6 may be flashed on locked BL as far as I know.
Hi, I am also wondering if I should unlock my bootloader. Anyway, camera futures are very important for me and I am curious if I will loose for example noise cancelling. I've seen the thread about DRM functions restoration but does it work with CM based roms?
Maciek602 said:
Hi, I am also wondering if I should unlock my bootloader. Anyway, camera futures are very important for me and I am curious if I will loose for example noise cancelling. I've seen the thread about DRM functions restoration but does it work with CM based roms?
Click to expand...
Click to collapse
Flat answer : No! 1. Either remain on Sony stock roms or 2. Say goodbye to your camera!
Maciek602 said:
Hi, I am also wondering if I should unlock my bootloader. Anyway, camera futures are very important for me and I am curious if I will loose for example noise cancelling. I've seen the thread about DRM functions restoration but does it work with CM based roms?
Click to expand...
Click to collapse
Good thing, you will not lose camera features if you use modded stock camera and noise cancelling will not gone(even in stock). The only thing that i see that u will lose are bravia engine though i glad that is gone(i need color accuracy). though all of it are included and usable even in UB like mxrom(best lp rom i have ever tried)
After contacting google and their twitter account and even calling in without a solution, and kept referring me back to if it met the requirements and is non rooted, modified or if the device was a USA purchase etc. i decided to just play around with what i had and here we go, it turned out to be so simple and for somewhat reasons google couldn't give this as a solution.
Solution to this:
*What you'll need:
- 2 devices ( your main, secondary [doesn't matter if it's a tablet, we're using it as a dummy to add the card(s)] )
- ... that's pretty much it lols
*Procedures:
1) on the secondary device download the android pay app and login to the same google account.
2) add the card that you want and verify and confirm it.
3) on your main device (in this case the sony xperia z5 / z5P) you'll notice that you'll be able to use and add cards with no more errors.
4) enjoy!
note: i tried to make this as simple as possible, let me know if you encounter any problems, as for the device did this for the error fix was my sony z5 premium international unlocked under a stock rom and non rooted or modified. so im not sure if this same case would apply for those who're rooted or modified but give it a try and let me know ^^
[deleted]
mattabyte said:
Worked like a charm, big thumbs up!
Google kept giving me crap like, "We do not currently support international or unlocked devices..." and, "If you've rooted your phone or unlocked the bootloader then it won't be able to use Android Pay..." even though I told them over and over again that my Z5P is 100% stock, locked BL, not rooted, etc.
I'll spread the word to friends of mine with Z5/C/P phones from various different countries of origin and let them know T&P works again with this trick.
Click to expand...
Click to collapse
Glad to hear it worked for as well ^^ btw, if you could please indicate your device status? Was it a rooted one?
[deleted]
Unfortunately i don't have second Android device?
Wish I can use it in Italy
Sometimes it's hard or impossible to use just a simple credit card.
hi there. I've had my XZ2 Compact (H8324) for a while now, and I'm looking into finally switching to LineageOS on it (preferably with MicroG instead of normal GApps suite, although it looks like it's not an option for now).
the problem is, I haven't tinkered with my devices for a while now - the last time I did that was on my Xperia mini pro about 7 years ago, and obviously a lot has changed since that.
it also doesn't help that the XZ2 Compact has a bit worse dev support than my previous device used to, and the documentation of the process seems to be a bit missing, too. I've seen some discussions link to the regular XZ2 forum for certain tools, so it's a little bit all over the place.
I'm not completely sure what's the procedure now, what tools should I use to unlock and flash the device, and what precautions do I need - for example, as far as I can tell from this thread, there's no need to fix the camera if I unlock the bootloader when running Android 10, but I'd want to make sure that it's correct. any suggestions on where to start the whole thing from would be very appreciated.
the device is H8324 (dual-SIM) running the latest available version of Android 10 - 52.1.A.3.49, and all the steps that require using PC will be performed from a Linux machine.
thanks in advance!
On most phones unlocking the bootloader wipes the phone.
Before anything backup, backup, BACKUP to an external device!
This can be tricky if you're not rooted and can't use an application such as Titanium Backup.
I use SMS Backup/Restore (Google Play Store) to backup my call logs and text messages and backup contacts using default contact manager.
If you're going to unlock and root on stock ROM camera should be fine.
If you're going to run a custom ROM check the forums for known issues.
According to this thread Sony Xperia XZ2 Compact [ROM][11] LineageOS 18.1 [OFFICIAL] (XDA)
KNOWN ISSUEs
The Sony stock camera does not work at the moment.
Click to expand...
Click to collapse
yeah, I've got the backups covered, my SMS are saved in the Signal backup and my contacts are all synced. thanks for looking out for me though!
from what I can tell, the LineageOS issue you quoted only affects Sony's camera app, while taking pictures with alternative apps works okay - and I'm fine with that. I just wanted to double check that there's no problems with viewfinder preview and the like, like it used to be with some Xperias in the past after unlocking the bootloader.
Hi,
I built and deployed the latest aosp 11 on this device. The phone is on the t-mobile network in USA.
All went ok but if I put the sim in the first slot, everything works except that the mic works ONLY if I am on speakers, cannot talk normally. Note that if I plug a headset, all works normally, but who can always use a headset?
If I put the sim in the second slot, most works including the mic, but sometimes I do not get messages. This is an issue specially when I need to get some token.
Anybody saw something like this?
Note that if I flush the stock Sony rom, there are no issues.
Thanks,
M.
Just an update, a few days back I rebuild aosp 11 and did a clean flash, exactly the same behavior.
If anyone do see this behavior and have a solution, please post it here.
Best, M
If anyone updated the OS to aosp 12 (or 13) please post your results here. I still have the issue shown in this thread.
Note that all seems ok with the stock android, it is only with the aosp 11 (the one I tried).
Me again and more on the saga of installing aosp on xperia 10 III. Since now I got a new daily driver (pixel 7 on which I installed grapheneos), I was able to test a bit more on 10 |||. I tried installing aosp 12. It worked and it booted, it looked ok. However after a reboot, it no longer sees the slots and the sim cards. I tried booting a few times, the same thing.
What is sad is that this exact behavior was on aosp 11 long time ago but was eventually fixed.
I am really disappointed by the very low quality of the sony aosp. They claim that they support it but when you install the aosp provided by them, it really does not work for the most basic things...
The hope to use this great device is when someone like Lineageos will release a version of their os for 10 3...
Q: what test is really done by Sony when releasing the aosp for a device, when something that simple does not work reliably?
Thanks,
M.
Just to complete my tests, I did install aosp 13 on the device. The installation worked but as with aosp 12, it did not detect any slots or sims. Reinstalled 11 and it does work but with the issues in this thread and another one from me.
I hope that someone from Sony will fix the issues otherwise why even say that they support aosp?
Thanks,
M.