yashsingh1/xdaforums huggingface dataset:
[Sony Cross-Device General] nailyk:
Really nice work!!

Yes Lineage try to keep a modded framework compatible with a lot of recent and old device blobs.

However, afaik those binary files are for modem and owned by manufacturer, not by OEM.

IIRC modem blobs are loaded into modem nvram so maybe platform independent?

Also maybe the fact the proxyController don't release the wakelock when incorrect value is returned could be considered as a bug and submitted to aosp gerrit?
[Sony Cross-Device General] ergoen:
Great work!! Applying a corresponding ugly patch to AOSP MM (6.0.1) fixes the issue (in amami) as well!! However, this cannot be the only way to fix it, in 6.0.0 (with 1.2.2 kernel) I didn't see this wakelock problem even with the java RIL code being the same.

Edit: the blobs are different so maybe that's it, I noticed that the string "RIL_REQUEST_GET_RADIO_CAPABILITY" is present in vendor/qcom/prebuilt/proprietary/msm8974/vendor/lib/libril-qc-qmi-1.so and libril-qc-qmi-2.so, in the old blobs (for 6.0.0 build) the string is not there.
[Sony Cross-Device General] SuperLamic:
I know that they are different, but RIL_REQUEST_GET_RADIO_CAPABILITY is present in the ones that we use. Maybe trying old one would be worth it. Radio capabilities were there even on MM...

edit: ugh.. now I realized it, if it wasn't present in the blobs, it returned error not supported and proxycontroller was happy with static values as it is now...
[Sony Cross-Device General] ergoen:
I believe I have found the offending commit regarding the msm_dwc3 wakelock. By reverting this the problem goes away: https://github.com/sonyxperiadev/kernel/commit/b27cb0a9d95e7295104cf5499c2da01703c4c0de

This is probably not the root cause for the problem, but I think it's a cleaner fix than to change all files back to 1.2.2 state.

edit: as rcstar6696 pointed out below this causes the phone to think it is constantly charging even after disconnecting it from the charger. This is not the solution to the problem, it only seemed so for when charging from the usb port..
[Sony Cross-Device General] rcstar6696:
As i said your fix exactly bring only back broken detection

Unplug your device from charger and you will see it shows charging all the time and this means its not a dwc wakelock but a charger wakelock

So use it if you want but it its totaly unusefull
[Sony Cross-Device General] ergoen:
Yeah, I noticed, was perhaps a bit too enthusiastic :).
[Sony Cross-Device General] rcstar6696:
Btw we have nearly fixed it i hope we finish it today
[Sony Cross-Device General] ergoen:
That sounds great! The reason I though it solved it for me was that it seemed to work when disconnecting from usb-port charging (didn't test the ac charger until now)
[Sony Cross-Device General] munjeni:
[MENTION=359497]jerpelea[/MENTION] you promised optimisation and cromatix optimisation for curently black camera on z1 line, we left 3-4 months and still have no news for camera. Whats going on? Do you working on camera and have plan to bring us promised camera, or you have no plan for it? Just curious. Be honest please, we do not want false hope! Very important for future market choice.
[Sony Cross-Device General] jerpelea:
i am exploring a 8mp@30 fps mode for imx200 but at this moment is just a proof of concept and i am not shure if it will work
[Sony Cross-Device General] munjeni:
Priority is low, very low or almost like no priority?
[Sony Cross-Device General] jerpelea:
since i am spending time on it now .... i will not assign a priority

you were invited to join the dev chat room and you refused
[Sony Cross-Device General] munjeni:
Thank you! Things is very clear.
[Sony Cross-Device General] munjeni:
Never.
[Sony Cross-Device General] erikcas:
how do we know?
[Sony Cross-Device General] m0d:
Using aosp camera, first thing noticed is it makes a lot of noise when focusing.

Manual exposure +1 +2 does not seem to have an effect,

But -1 -2 seem to work very very dark

Front cam preview is upside down, but saves right side up but grainy

Freedcam makes less noise focusing, but same as before slow and not always clear.

Max size 3840x2160

+ exposure sometimes appears correct for a second but then back to default + value, - dark

Also front cam preview upside down, Saved pic also grainy

All in all, same same. No improvements

Noticed in latest updates no mention of them, but no change for 2years.

A shame since I loved x10mini pro, camera was great and lowlight too. And nAa did great work.
[Sony Cross-Device General] davidteri91:
Uh xDDD

Inviato dal mio F8131 utilizzando Tapatalk
[Sony Cross-Device General] munjeni:
For me good enought...
[Sony Cross-Device General] optimumpro:
Oh. That's an easy one: Sony Aosp "dream team" has been pretty consistent in one thing: they never had a usable camera on any Android version. Never, ever... . Had it not been for CM's use of JB stock camera blobs, we would have still had a camera with the Down syndrome (Aosp camera). But CM has switched to Sony AOSP trees and they are no longer working on most Sony devices. So, get used to a disfunctional unusable camera or use Lillipop...
[Sony Cross-Device General] munjeni:
Stock blobs is not working since stock blobs require locked bootloader? Ok, I have some good news for all interesting for fake locked bootloader with all valid keys, I will not do anything to camera or any android for sony since I was temporary baned (thanks to some guys over here), allready disapointed, but hope somebody do something, here is PoC for you https://xdaforums.com/showpost.php?p=70330773&postcount=1575 and some tools which I done for helping PoC and dealing with ramdisk things (last two links in my signature)
[Sony Cross-Device General] fluffi444:
This is really nice work... Hopefully you'll change you mind again to keep on your good work.

For me I even do not know want happend here - But do not let kidz demotivate you!

One question to mounted TA: Do you have in Service Menu "Service Tests/Security" MARLIN etc Active with given key?

Or is ist still "[Unkown Error][Active]" as we know it from "simple" DRM fix?
[Sony Cross-Device General] vikash1994b:
Hi, few devs has managed to build leaneage os nd carbon rom based on stock kernel and blobs for Z3+ and z5 so camera is working fine with stock like quality.

Here is the link- https://xdaforums.com/xperia-z5/orig-development/cm-14-1-lineageos-t3536846

Is it possible for other xperia like z1,z2 nd z3?

Credits:-
[Sony Cross-Device General] munjeni:
I am sure I will not since in most case I will get ban again (as allready got as a result to things which was happened in this thread). But I was very motivated to do something for camera, now demotivated.

Apsolutly the same like having locked bootloader!
[Sony Cross-Device General] munjeni:
We have no stock kernel for nougat! But everything is possible in case everybody involved and not unfriendly!
[Sony Cross-Device General] Myself5:
And as always uninformed optimumpro is uninformed. Check the CM ivy and sumire trees ;)

Credits where credits are due. I was part of the collaboration between Carbon and the Lineage Developers to get that going. HOWEVER, the main work was done by the others. By the time I joined ivy was almost fully working already, and all I had to to was modding the ivy tree for sumire (I even messed that one up, as I forgot to rename the product device, lol).

So huge thanks should be going to [MENTION=4329876]Olivier[/MENTION] [MENTION=513620]Quarx[/MENTION] [MENTION=3506409]cdesai[/MENTION] [MENTION=2492127]Kali-[/MENTION] and [MENTION=7062343]banmeifyouwant[/MENTION]

We hav't had one either :p The kitakami trees are using the M based blobs and kernel source, as N just got released yesterday. I am in for the game. Z3 and Z3C are getting dustier every day, and I can't stand that any longer. I remember you saying you had the stock kernel with stock blobs booting on Nougat before? Would you be able to share the device trees and the kernel for that so others can take a look at it?
[Sony Cross-Device General] munjeni:
This one https://github.com/munjeni/android_kernel_sony_msm , device tree is deleted from my hard disk and all patched blobs which I used is deleted too, the libshims which I done also deleted but maybe you can see it in this thread and blobs if I have attached it to the attachments. That kernel requires propper adreno which you can see in one of the my posts in this thread... I was very close to get camera working, you can see also all logs and things provided, so if everybody want to continue on me just read whole thread to understand status of that kernel and things
[Sony Cross-Device General] optimumpro:
This is at least the third time you post ridiculous statements against me starting from phony claims that I gave you no credit for using your modified CM kernel as a base etc... .

CM no longer works on Z1, Z1c, Z2, Z3 and Z3c. I checked their github a couple of minutes ago and there is not even a N branch there. Next time try to read and COMPREHEND the post you are trying to answer. Cheers....
[Sony Cross-Device General] Myself5:
You are starting that again? For real?

Hum, when did the sumire and ivy cm-14.1 branches appear? Oh right. only a week ago when everything was working. Might that potentially mean that there are private trees existing for other devices that are work in progress too? Nobody knows exept for the ones that WORK one things instead of sitting in a corner crying about the bad bad devs setting their priorities to newer devices I guess. Well you wouldn't know, thats for sure.

Now go and fork my kernel yet another time and leave me alone or get your things together and JOIN on the bringup.

It's up to you.

EDIT: After rereading this post might be a bit harsh: My intention was not to insult you. My original intention was to bury that kernel thing and offer to join on the stock bringup efforts. Probably expressed the wrong way. My bad.
[Sony Cross-Device General] nailyk:
Please no need to stab each other in the back.

Everyone here subscribe for the same reason, improving Sonys devices. We all know that stock blobs are a pain because of this DRM protection.

SODP team are working on an open sourced kernel and compatibles blobs. Maybe it is not the better choice but it is a choice and no need to blame them each time they talk about it.

AFAIK the only other solution should be rewriting all the blob set on an open sourced way. A lot of you are smart enough to do it, and even it is crazy, it should be less time wasting than barren debates on things nobody can control.

We have all the leaked sources to understand how camera is working, maybe some documentation can be accidentally found on internet but it is a huge work, I admit.
[Sony Cross-Device General] munjeni:
One of the reasons why my work now and future work is no more open source. I do not believing why all fights is need over xda, is that realy need? Why not just enjoy friendship and group devs into one and make things much easier? Please do not again! Stop please.
[Sony Cross-Device General] optimumpro:
I have never started anything against you. You are the one who always come up with phony claims.

Your kernel? It is not your kernel. It is CM kernel that you modified, which I later modified and anyone else can modify. Copying and pasting doesn't make it yours.

You sound like a 16 year old bully. Grow up.

Anyway, I have no interest in talking to you any longer. Cheers...
[Sony Cross-Device General] rocker00:
i totally agree with you, always fighting and arguing instead of concentrating on the goal and work like a team,everyone has his own thinking it might be right and it might be wrong this in normal and it's not a problem at all,if everyone provide his ideas whatever it's right or wrong sure in the end you will achieve the goal,also since everybody here is working for free and waiting for nothing then there is no need for any kind of fighting at all and everyone must show respect the the others, instead of this have fun and don't stress yourselves !.
[Sony Cross-Device General] jerpelea:
sorry for jumping in this

everybody blames us that we don't do anything and we dont release fixed stuff

has anyone checked the oss camera on X ?

or maybe z5

we never claimed that the oss code can be as good or provide the same features as the official one (the same happens with all oss ex: nvidia,intel,amd...etc)

there are limitations on the old devices and we apend a huge amount of time to understand it because ...it is simply different

you all have "your" patches and "your" kernels but last time i checked the kernel was forked form kernel.org by a chipset manufacturer then forked from there by a phone manufacturer that released the copyleft sourcss for a specific device.

and since you all use gpl code when was the last time when your patch has been pushed to github or upstream?

?
[Sony Cross-Device General] munjeni:
Jerpelea but but you promissed 2-3 months ago optimised chromatix for imx200 in blobs v7. We waited and waited and waited... and didn't received chromatix in that v7 blobs. Don't annoynce somethong like that if you are unable to make that happen please. In my case I wasted my free time with aosp camera and finaly figured out that problem is not kernel and hall but problem in blobs, it was soo late since allready got disapoint before found that, not only me but hope everybody who worked hard on it. If you open rhine forums you can notice silence, dead forum, thats because everybody got dissapoint :( Nobody can develop and improve when major thing is missing, working blobs. Anyway I still apreciate your constant and hard work on Sony devices and didn't forgot xperia go and your work on that device, it was very correct.
[Sony Cross-Device General] jerpelea:
the cromatix is qualcom and is just a big table if values so feel free to fix it or google for the tool

the biggest problem was to find a proper configuration that can provide sensor initialization and calibration
[Sony Cross-Device General] munjeni:
But you have all proprietary and propertly source code, not?
[Sony Cross-Device General] optimumpro:
He probably doesn't have it and in this case, he is as blind as every one else. Otherwise, if he had the sources, it wouldn't be that difficult to make the appropriate changes. Notice, how he is pushing you towards Xperia X. Just buy it and you'll have Nougat. Sony wants your $700 every two years. They want it so badly that they won't even publish the dumbed down sources...

You should ask him why Sony drm protect their blobs? Surely, not because they are afraid of reverse engineering. DRM doesn't prevent reverse engineering, it prevents the use. So, why does Sony not want you to use their blobs on a Sony device that you bought from them?
[Sony Cross-Device General] davidteri91:
Sony¿? likes all other .... Don't BLAME Sony only ... If you are not capable to develop please let developers do they work .... and don't cry in every post ...

Inviato dal mio F8131 utilizzando Tapatalk
[Sony Cross-Device General] optimumpro:
You and myself5 would do everybody (including yourselves) a favor by stopping these idiotic and childish personal attacks. I don't blame you, it is just your immaturity. You think only you can cut and paste. What a shame...
[Sony Cross-Device General] davidteri91:
Were your words .. make me reply you .... And I will repeat like all others OEM ... Sony supports every new model .... You are not obligated to buy every single new Sony phone .... if you don't like Sony then go ahead with other OEM and you will stop cry about camera on not official Sony releases ....

Inviato dal mio F8131 utilizzando Tapatalk
[Sony Cross-Device General] optimumpro:
My words were not directed at you or myself5, but at Sony. You didn't like the message and decided to attack the messenger. That's behavior of a dope. :)
[Sony Cross-Device General] nailyk:
Except the chromatic for imx>200, sources of 4.4 are on internet.

Why a rewrite from scratch, instead of useless-time-wasting-fight, is such a bad idea?

If someone had MIPI doc it will improve a lot those sources reading btw ;)
[Sony Cross-Device General] :
Please try to remain civil here. It seems the discussion was/is getting a bit heated. Perhaps private message would be better for some of this as opposed to open forum. Remember, this is supposed to be fun, right? I'm not going to remove any posts here or give any "official" warnings. I just ask you all to take a deep breath, relax, and have fun. :)

Sound good?

Thanks!

The Merovingian

Senior Moderator
[Sony Cross-Device General] munjeni:
No sense wasting time on this thread, realy.
[Sony Cross-Device General] munjeni:
Don't agree with you in one case, why wasting rime in fixing bugy closed source blobs when we allready have a working stock blobs, is not better idea wasting time with working blobs?
[Sony Cross-Device General] jerpelea:
the cromatic is almost the same for imx2xx and it will make life a lot easyer
[Sony Cross-Device General] nailyk:
IDK, that is why I ask.

Everyone here fight about problem faced with the stock one. So a solution could be stop using it and doing a rewrite from scratch. A lot of you are able to do this.

Also those old sources are kitkat so not drm protected (but probably only 3.4 compliant).

Obviously I'm not talking about c/p which will be illegal, but reading them, understand how camera work, then rewrite.

It is a big amount of work. But this way everyone can work on it and can provide lifetime upgrades.

But I'm talking about something I'm not able to do, so it is only hypothetical :)
[Sony Cross-Device General] munjeni:
I still not understand something, why aosp imx200 is max 8mp? Our sensor is 20mp, so quostionable is why spending time on something which probably will never work corectly? Who guarant that it will even work? All my hope to AOSP open program is down till after I read posts after this one https://xdaforums.com/showpost.php?p=70546028&postcount=649 to the last one, I am pretty sure we ending here with wasted time and wasted waiting.
[Sony Cross-Device General] nailyk:
Check your PMs in a few :)
[Sony Cross-Device General] erikcas:
nothing personal, but [MENTION=359497]jerpelea[/MENTION] having all proprietary and propertly source code maybe the part of the assumption that causes a lot of misinterpretations and dissapointment here.

Another thesis about that: Even if he has, should he be allowed to use it?

There are big financial interests from multiple companies involved in this part of the code. Probably lawfully well secured by tight contracts.

Note these are my assumptions.

Afaik we are well supplied with various blobsets for sony devices. We should be glad.
[Sony Cross-Device General] munjeni:
Yes sure! Nobody says we are not glad, we are glad indeed for what Sony doing and for what jerpelea doing for us, but we are I think deserved a bit of honests and respects since we are directly or indirectly helped making some models more popular, right?
[Sony Cross-Device General] m0d:
Sony advertised open device dev, which means they should be accountable for missing and not properly functioning blobs.

When buying device users should be able to use it.

In my case both stock and custom rom has major issues.

As everyone here knows camera and audio majors issues on custom.

Due to these I decides to stay on stock but:

In stock, firmware has serious issue where phone becomes unresponsive: dead, all of a sudden, no way to reboot, with buttons nor reset button beside sim.

Not sure if it was bootloader or kernel issue, or maybe motherboard issue, which was what service centre said.

This happened even to my replacement device while phone was in service, too. But, it magically healed itself.

So, when sony sells device and there is problems with what they say they support and normal stock experience,

We should be glad.

Also focusing more on latest devices is a strategy that forgets that people with older devices are going to be buying a new device eventually, sony can give them more incentives for it to be a sony device by fixing the current peoblems.

If they do have source, it makes no sense not to have audio working.

And stable camera too.
[Sony Cross-Device General] nailyk:
I think [MENTION=650622]erikas[/MENTION] explain something different. We should not mix commercial decision of the manufacturer and what a few people do for open source. Yes Sony had a really bad politics for they roms with this DRM thingamajig, but I think what he said was AJ do his best to help us, making compromises between this legal problem and open source improvement. We should thanks him trying to help us. He is playing with fire.

That what I understand.

Also please stop complaining about DRMified blobs, it is a pain, a shame, whatever but nobody can change that and even if there is no result for now, everybody try.
[Sony Cross-Device General] optimumpro:
I don't think this is relevant at all. No one is forcing Sony to publish their code: the blobs we are talking about have already been published, so, whatever financial interests are involved, they are NOT touched in any way. The creepiness of Sony by making these blobs unusable on custom roms is at issue. This is a corporate policy that pushes users to buy another device. By the way, I am not aware of any other OEM that does that. But guess what, Sony is shooting itself in the foot: just Google "Sony disappointing smart phone sales" and you will get the picture. I don't think they ever had profit in the smart phone division: Well deserved...
[Sony Cross-Device General] erikcas:
Exactly. No one is forcing Sony to set up a development program for opensource. I think you are not able to distinquish OEM Sony from Sony developerworld.

Name me 10 OEMS who provide you blobs on their website, provide you with devicetrees and kernel on github which is quality-wise equal to stock? And what is their interest of doing so? Which philosophy is behind that?
[Sony Cross-Device General] munjeni:
I am confused whith one thing, is all this work work from jerpelea and co without any oem help or there is still some help from oem? Noticeable thing is guys is not enought skilled to make camera work, hope I am not wrong? Whats going on anyone explain? Four months and still no camera, this have no other means than: 1. He working but have no enought skills, 2. He apsolutly not working on it. Nothing else. If option 1 why not ask help from oem? He deserved help.
[Sony Cross-Device General] erikcas:
That is quite something you are saying about a sr recognized developer.

I cannot look inside Sony as a company, so I donot know, and I donot have and want to know. But, let me link you to a few posts from http://developer.sonymobile.com/

Maybe it will help you understanding, maybe not. It makes sense to me in any way, regarding expectations

http://developer.sonymobile.com/201...-camera-available-for-experienced-developers/

http://developer.sonymobile.com/201...-devices-with-new-aosp-device-configurations/

http://developer.sonymobile.com/201...w-supported-devices-improved-camera-and-more/
[Sony Cross-Device General] munjeni:
Thats very clear now.
[Sony Cross-Device General] adinkwok:
Before the discussion is continued, I want to make a statement. The participants of the on-going discussion(s) are lucky that [MENTION=5302753]The Merovingian[/MENTION] just came to swing by to keep things in check rather than having the problem escalate even higher.

With that said, how come I am already starting to see some flame inducing comments, which can be taken out of context for numerous reasons? Such conversations do not need to happen here, please watch what you write on the internet. Context is hard to portray through words written in a sentence, which is why themes like sarcasm do not work very well. Whether it is sarcasm, questions, anything really; make sure that you are mindful with what you are saying, and that it may not backfire on the community.
[Sony Cross-Device General] munjeni:
I have no more questions. Unsubscribed from this rhread. :good: