yashsingh1/xdaforums huggingface dataset:
[Sony Cross-Device General] munjeni:
You must think about peoples who don't have PC for flashing that apps_log!!! Solution which you provided is soo stupid! You can use file based partition, for example misc.ext4 and put it to the loop on boot time!
[Sony Cross-Device General] davidteri91:
Do the changes and send the PR ....

Inviato dal mio F8131 utilizzando Tapatalk
[Sony Cross-Device General] munjeni:
Revert first and wait someone make a proper patch!
[Sony Cross-Device General] davidteri91:
This seems for me fix == NULL .....

Inviato dal mio F8131 utilizzando Tapatalk
[Sony Cross-Device General] erikcas:
I totally lost you here...

Verstuurd vanaf mijn F5121 met Tapatalk
[Sony Cross-Device General] erikcas:
Now where is that tutorial again to unlock bootloader without pc?

Still very lost

Verstuurd vanaf mijn F5121 met Tapatalk
[Sony Cross-Device General] davidteri91:
[MENTION=985241]erikcas[/MENTION] ... How a person without PC .. can install fastboot images ????

Inviato dal mio F8131 utilizzando Tapatalk
[Sony Cross-Device General] erikcas:
You prevent me from editing my post here... You see how lost I am?

Verstuurd vanaf mijn F5121 met Tapatalk
[Sony Cross-Device General] munjeni:
Kidding me? For example this one no need fastboot -> http://xdaforums.com/showpost.php?p=69426511&postcount=1
[Sony Cross-Device General] davidteri91:
Sure me too is a good night to pick a Heineken and lost our minds xD xD

Inviato dal mio F8131 utilizzando Tapatalk
[Sony Cross-Device General] munjeni:
You are lost for sure since you are out of ideas. How to unlock your bootloader without a PC??? Simple:

dd if=/storage/sdcard1/TA_unlockedbackup.img of=/dev/block/mmcblk0p1
reboot

Enought?
[Sony Cross-Device General] davidteri91:
Read WTF you wrote ....

How to install:

You must have unlocked bootloader bla bla bla ...

A person without PC .... I want see how it can be done .....

Inviato dal mio F8131 utilizzando Tapatalk
[Sony Cross-Device General] erikcas:
Kidding me? You start that post with some decent language about unlock bootloader.

Verstuurd vanaf mijn F5121 met Tapatalk
[Sony Cross-Device General] munjeni:
Download that zip using your android chrome browser, reboot to the recovery and simple flash! There android 7.1.0.zip which I provided is flashable zip! Enought?
[Sony Cross-Device General] davidteri91:
Suicide time ... [emoji1] [emoji1] [emoji1] [emoji1]

Inviato dal mio F8131 utilizzando Tapatalk
[Sony Cross-Device General] munjeni:
And? Whats not clear? E.g. I have ta backup from unlocked bootloader two years on my external sdcard. And also the same backup of the locked bootloader. And booth things I have done e.g. on my friend PC 2 years ago! E.g. now I have no PC. Whats not clear to you?
[Sony Cross-Device General] davidteri91:
Why you want write the rules ??? When an official way is present .... This stuff is like that hacked camera idea ... Man your ideas are not ideas .... Sorry for be rude but is the true

Inviato dal mio F8131 utilizzando Tapatalk
[Sony Cross-Device General] munjeni:
Thats your problem. I not going to debate with you here
[Sony Cross-Device General] munjeni:
http://xdaforums.com/showpost.php?p=69637391&postcount=544
[Sony Cross-Device General] davidteri91:
Since you are the unique experienced developer here .... Why you refuse to join us in hangouts and share the ideas in a clean and proper way but no ... You ever start "your" crazy ideas .... And that is not the way ......

If developer world say ... Use EMMA to flash ftf and use stock then that is the way to get stock .... And not revert with a modded recovery .... Jesus ... You make lost my mind

Inviato dal mio F8131 utilizzando Tapatalk
[Sony Cross-Device General] erikcas:
oke let me clear it up for you, once and forever.

Sonyxperiadev repos and development have a buildguide as a basis for users.

It explains how to build and flash AOSP roms from sonyxperiadev repos. It ASSUMES you have a pc to fastboot flash boot.img, userdata.img and system.img

This ASSUMES you have a pc. It also ASSUMES you know how to use Emma to flash required (latest?) stockroms with proper bootloaders.

As [MENTION=359497]jerpelea[/MENTION] explained multiple times, the sonyxperiadev repos can be taken as a basis for other custom roms.

The fast majority of customroms use a recovery that is able to flash flashable zips.

If you need customized partitions, modified buildsystems for that, you as a real developer, are free to modify this. But the sonyxperiadev project does not support it.

So if you need a solution for pc-less users, fix it.
[Sony Cross-Device General] munjeni:
I was done most of part but lazy to "shim" and smali android stufs. There was no sense wasting time with legacy rhine, now in almost low activity forum. Agree?
[Sony Cross-Device General] munjeni:
Ok, agree, but I not going to fix anything, just reported that your patch breaks apps_log partition and cause trouble to everybody who was not able or have no skills to restore apps_log partition. I am in hope these commit will go reverted and make wait somebody PR proper patch.
[Sony Cross-Device General] erikcas:
I think you comletely missed the part before the last sentence
[Sony Cross-Device General] davidteri91:
As ever .... This answer me some question .... Have a good day/night

Inviato dal mio F8131 utilizzando Tapatalk
[Sony Cross-Device General] munjeni:
What?
[Sony Cross-Device General] munjeni:
Thats a my way, I don't uses emma and most of peoples too. You guys made now debate with nothing, just because I wrote that your solution is not a solution. I can say again thats not a solution.
[Sony Cross-Device General] munjeni:
You answering byself I see, I think better idea ...go for that beer finaly and free your brain
[Sony Cross-Device General] davidteri91:
Look I am 100% sure that "bear" can do it better .....

Inviato dal mio F8131 utilizzando Tapatalk
[Sony Cross-Device General] munjeni:
You can go finaly
[Sony Cross-Device General] adfad666:
This is a beautiful button. It has one function, but it can fulfil all of your wildest dreams/desires/fetishes. Use it.
[Sony Cross-Device General] erikcas:
You are free of using Emma or not. That is awfully fine. If a solution is not a solution for you because you want things to be other then AOSP from sonyxperiadev, you are awfully free to use that source and modify it to your needs. Totally free. If you help (pc-less or none-pc less) users with that, please do.

But what you are doing is bashing people around that they are totally wrong. You did that a short time before with your bashing about that camera, implying non-support from sony.

You were shown by a 3 lines commit, later cleaned to one line if I remember well, that you were totally wrong.

And some days after, improved blobs were released.

And now you are doing it again! What works for you, fine! Be my guest, fork the repo, modify the fstab and make people happy.

But donot say the fix is no fix because it does not work for you.

Again, if you want to use those sources for your intentions, and philosophy and vision of custom roms, use them and modify them to match that philosophy and vision of custom roms.

Since you

ARE

an

RD

, you should consider it as your DUTY to come up with solutions for users on XDA that support your intentions, and philosophy and vision of custom roms. You cannot simply bash people that contibute to or develop for a project with another intentions, and philosophy and vision. And shout "revert the commit and let someone fix it." YOU are RD, with intentions, and philosophy and vision.

So, use your keyboard for what it is designed for and create some genius code!
[Sony Cross-Device General] munjeni:
I don't have idea about what is your button for, but my button for all you on this thread

I'm finish here and say you bye! You can continue to debate byself here :good:
[Sony Cross-Device General] erikcas:
I think you can't
[Sony Cross-Device General] mcgi5sr2:
OK thanks for that all.

[MENTION=4120742]munjeni[/MENTION] thanks for the USB patch. Would you have any problems if I submitted it as a Pull Request to the official sonyxperiadev github? I think its a fix that would benefit all users.

as for the misc partition patch, its been good to get more info on why I was having to use emma to reflash. However most of the discussion that was useful was the first two comments. I understand people want to vent their frustrations, both User side and Dev side. This thread isn't for that, and I don't want to see another useful thread die because of it.

I also understand that as English isn't a first language often what people say comes across a lot more aggressive than intended. Please stay civil and on topic.

I am not a Mod, but just tired of seeing this kind of thing all over XDA
[Sony Cross-Device General] caki25:
Hmm, this might explain why i can't boot any stock ROM :laugh: okay, either I stick with AOSP for the moment, or flash the app_logs partition from ftf and back it up... :) It's at least good to know :)
[Sony Cross-Device General] davidteri91:
Yeah as Sony developer site says ... You need use Emma to get stock fully working and not using crap way (custom recovery)

Inviato dal mio F8131 utilizzando Tapatalk
[Sony Cross-Device General] munjeni:
You made that recovery crap, and not only one but all recoveriies crap. You made now that all well used recoveries and its backup and restore features totaly unusefull because you are soo smart and sadly you realy believing that.
[Sony Cross-Device General] munjeni:
Ps Not ofense but true. And one more thing you didn't know anything about that thing which corupts that apps_log until yesterday so please don't say anything more about developer site because that have no relations to your commit which you done to fstab.
[Sony Cross-Device General] davidteri91:
I know man .... I am not offended ... But the true is ... If you want use aosp .... Use aosp and you know the method to get it up .... Same for stock .... The proper way is using Emma .... Not multirom ... Not custom recovery .....

Inviato dal mio F8131 utilizzando Tapatalk
[Sony Cross-Device General] munjeni:
Thats not a true! Everybody including me using that good recovery feature aka backup and restores for years and apsolutly it worked perfect! Nobody can call its not a proper way! And you know that too! And you guys made offense to me yesterday, grouply, but ok no problem, anyway your sounds is ok this day I like :good:
[Sony Cross-Device General] munjeni:
Forgot to say something. Apps_log partition is ext4, I have no tried to change emmc to ext4 line in fstab but probably changing that in fstab probably will end up ok in AOSP without corupting that partition!
[Sony Cross-Device General] :
OK folks. I didn't clean any posts, since most can be called semi-constructive. But, let's try to keep things civil in here. And if things here just really bother you, perhaps unsubscribe, or at least add people to your ignore list if needed.

This is a dev talk thread, let's stick to dev talk. Nothing personal. :good:

Cool? :cowboy:

Darth

Senior Moderator
[Sony Cross-Device General] Masterblop:
New blobs: http://dl-developer.sonymobile.com/eula/SW_binaries_for_Xperia_AOSP_M_MR1_v06_EULA.html
[Sony Cross-Device General] munjeni:
[MENTION=359497]jerpelea[/MENTION] is solved camera focus and is camera now not dark anymore? Thanks
[Sony Cross-Device General] jerpelea:
it is better but not final
[Sony Cross-Device General] munjeni:
Is possible to integrate xml userspace for chromatix so we can tune byself these arrays? Just idea! It would speedup fine tuning camera and in same way more peoples would be involved in tuning that!
[Sony Cross-Device General] tomascus:
So, are you planning on excluding the rest of us?
[Sony Cross-Device General] DarkJoney:
Guys, if I could help with something, I could try to do something useful, cuz I am interested in high-quality camera.

Is there any possibility to port MX5 camera to Z2?
[Sony Cross-Device General] munjeni:
Nothing sony related but closed source qcom proprietary camera. I have searched google for imx200, found only one git with qcom proprietary source code but it have no imx200, in anyway I think thats leaked source code and we can't use them either. Sony camera hal is linked with libcacao_core and libcacao_system, we can't avoid that. What about if we implement sony v4l2 camera from stock kernel to 1.3.3 kernel? Its just an file! I found v4l2 android camera hal source code... see attachment! It uses jpeg and skia :) Probably it can be realy good start pont for work with sony v4l2 camera kernel module and this one android generic v4l2 camera hal! What you think guys, we can avoid qcom and sony with this? I realy have no plan for changing phone, I will use it until display got out of phone, than will again buy new display like done allready one time, my phone is like new one, new battery, new display, some small scratches on aluminium but the rest is in perfect condition, it just missing fully open source code :laugh:
[Sony Cross-Device General] tomascus:
I was actually thinking of using the caf HAL https://source.codeaurora.org/quic/la/platform/hardware/qcom/camera/tree/?h=LA.BF.1.1.3_rb1.13

I'm not sure, but SultanXDA got one working with OnePlus One.... :eek:
[Sony Cross-Device General] munjeni:
I don't know, only which I think about camera half green screen is related to camera blobs? Not hal related? For example it is somehow messed up with dual camera things in blobs. I have tried 1.2.2 kernel to get camera but still can't get camera any way :( One of the reasons why I switched to stock kernel is that sony v4l2 kernel hal module, it can be ported to 1.3.3 kernel? That would be ideal thing if can be possible using that with generic android v4l2 camera hal. We never will have good camera with sonyxperiadev blobs, never! We always will need to wait for new blobs on every new android source code. We need to somehow avoid that, for example make new camera hal without any depended blobs! Did you look into sony v4l2 kernel camera source code?
[Sony Cross-Device General] tomascus:
I did, it looks super barebones and I don't know how it functions just like that. And I thought v4l2 was merely the kernel interface, the actual camera HAL needed to be implemented.
[Sony Cross-Device General] Myself5:
Check the SXDev camera hal. Thats based on the 1.3.3 CAF HAL, that might help you getting 1.1.3 working.

I honestly think this is a very stupid idea. If you people would stop crying about not getting mouth ready pieces of code served, how about you try fixing 3.10 instead of starting over with 3.4????

At what point is fully starting over with a known not to be working plan (trust me, 3.4 and new cam blobs have been tested for way too long now) a better idea than fixing a already working project? All this does, it bringing up people pussing about, and splitting the dev community.
[Sony Cross-Device General] tomascus:
Myself5 coming in a little hot :silly:

Thanks for your input though, perhaps you're right that it isn't such a good idea. I thought you moved on from msm8974 long ago hahaha.
[Sony Cross-Device General] munjeni:
Camera never worked good on any 3.10 kernel for rhine platform! I somehow thinking that we will newer have camera working on 3.10 since its branches is few times changed on that kernel, the last one branch totaly broke camera, previous one also had not good camera, optimimpro is right about that, it just make us happy on one side and on another side forcing us for bying new phone, I no want to change phone in revolt to that, I have z1c 3 year old, it will be 6 years old in next 3 years. Other than that 1.3.3 kernel working realy good, camera only problem & closed source camera
[Sony Cross-Device General] munjeni:
If we start fixing it branch will change soon or prety soon, no point fixing it. Beter idea is using old phone for years until vendor gives us what we need.
[Sony Cross-Device General] Myself5:
Still owning leo and aries, in addition to sumire. Sumire is currently used as the Carbon CR5.0 bringup phone, so I am currently using leo as a DD. I KNOW the 3.10 1.3.3 cam has issues. But it is a HAL or Kernel issue. So rather than trying to port some closed source ****up, you should go with the OSS stuff that is at least somewhat working.

That is a lie. Rhine and shinano have the same camera sensor. End of 1.2.2, cam was working flawless, I know that for a fact. I used it on my Z3C.
[Sony Cross-Device General] munjeni:
Why branch changed when it worked? Yes, because xperia z5 and X needed new kernel, but why not used 1.2.2 branch to add support for 5 and X? We are forced to have new phones! Thats not real develoment! And who know if it is kernel isue, hal isue, or blob isue? No body know that! Dual camera I think messed whole things, including blobs messed too. Sony have almost the same camera sensor on booth z1,z2,z3,z4,z5...etc, but if you look into diferencie between for example 1.2.2 and 1.3.3 there is a huge diferencie in camera, why when camera sensor is almost the same??? To make thing "non portable?
[Sony Cross-Device General] aquaboy11:
Exactly this. If it keeps going like this there will be pieces of information spread across devs without them wanting to share anything, just for the sake of being able to say "This is my work.".

There is a point in fixing it. As development continues, Android's becomes closer and closer to the Linux kernel, and should become easier to port without heavy modifications. Like [MENTION=3816568]Myself5[/MENTION] already mentioned, development for 3.10 should be easier than 3.4.

Agreed. I think we should be working with the open source stuff too. The more people working on it the better it might get, and eventually we might not be dependent on closed source anymore. I hope [MENTION=6594010]mkdmc[/MENTION] will join in instead of sucking developers out of this thread by convincing them closed source would be better.
[Sony Cross-Device General] munjeni:
Thats not open source, thats partialy open source! Camera blobs is fully closed source! I don't know if somebody interesting for v4l2 generic hal, I am interesting and I will not mess with closedsource camera, i will go this way:

1. extract function primitives from google default camera hal for referencie

2. port back sony v4l2 kernel hal (probably I will continue with stock kernel 3.4, in most case)

3. start porting android generic v4l2 camera hal by looking into google function primitives, make excatly the same functions names to v4l2 hal

4. everyday port one function

5. in hope I get no disapoint, finish them in next 6 month
[Sony Cross-Device General] kholk:
We should clarify the meaning of the word "progress".

About 3.4 vs 3.10 .... when I ported the first 3.10 kernel to MSM8974 (I was using Honami at that time), Xperia Z3+, Z4 Tablet and Z5 (MSM8994 devices in general) didn't even exist... but:

- First of all, Xperia Z5 didn't need 1.3.3 kernel branch, it was Xperia X, as MSM8956/8976 is supported only by that one.

- Second thing, I could have backported one device and lil SoC support to the 1.2.2 branch, wouldn't have been TOO MUCH hard but, instead, we chose to port all the current Sony devices to the new 1.3.3 branch: do you actually see which one of the two things is harder and more time consuming?

- Third: did you notice that what we do is unifying the devices so that if you fix ONE of them, you basically fix ALL of them?

- Fourth and last: We don't remove old kernel branches, NEVER!!!!!! Noone stops you from using old software, so your point is basically NULL.

Forced to have new phones?! That's really false.... Just see by yourself: we are continuing to support really old devices, like Rhine platform, doing our best. We are providing always a new, fresh base for really old devices, thing that, from what I know, noone does (because noone has an OEM on his back that compiles proprietary code for open source projects!!!!!).

If there's any problem, and you say you're a developer, you should HELP us instead of just blaming us "just because".

And remember: we all are humans, not machines. We have our lives, our job, our family and our passions. We are not paid to do this, but doing it in our free time, satisfying our passion: development.

You should understand.

Have a nice day!

--kholk
[Sony Cross-Device General] drakonizer:
I have to disagree here, for three reasons.

1) If we get the camera to work with a 3.4 kernel and stock blobs, the quality would be much better compared to the AOSP blobs from Sony. I agree, it would be a pain when a new version of Android gets released, but most people here have been using cm12.1 and its derivatives for 2 years now, and nougat can easily run for another 2 years. Meanwhile we can switch to the 3.10 kernel if it ever becomes stable.

2) Most of the great devs for the 3.10 kernel have either moved on to newer 64bit devices, or have been awarded with newer phones for their contributions. Their attentions have shifted, which resulted in the number of commits for msm8974 decreasing over the past months.

3) Sony will keep releasing newer phones and Jerpelea will have to keep switching branches to support newer devices. Each new branch comes with even less support for msm8974 devices.

It's also ironic to note that Sony phones that aren't a part of the Open Devices program have much more stable versions of newer Android releases than the ones that are.

I do agree with you to some extent. [MENTION=6594010]mkdmc[/MENTION] should share whatever ideas he has with everyone on this thread so that more people can contribute. I also think open source is the best way to go, but the 3.10 kernel has had little progress in stability for rhine and shinano devices. The charging bug and camera issues have stuck with us ever since 1.2.2

EDIT: I see this thread has managed to capture the attention of even the best among the Sony devs. That's good to see!

---------- Post added at 09:01 PM ---------- Previous post was at 08:53 PM ----------

As far as I remember, there was remarkable progress in camera during the 1.2.2 times, but at the end, there still were issues of a laggy preview, buggy focus, and inability to take photos in low light. All these were due to calibration issues in the blobs, as far as I know, and were fixed later with the blobs release for 1.3.3.
[Sony Cross-Device General] Myself5:
And your talking **** again. Z1 up to Z3+ have the same sensor. All have the same problems too btw. Z5* and X* have a different sensor. Before complaining, you should fix your facts.

The qcom source leak you linked even SAID msm8226-kk. OFC that is what jerpelea used for 8974 on M. Makes totally legit sense....

Cmon, seriously. Instead of complaining you really should either fix your facts, or work with others on fixing 3.10.
[Sony Cross-Device General] munjeni:
Who say " the same"?? I say ALMOST the same!

Fixing 1.3.3 no. Reason: no point wasting time with something which have broken camera, I even don't know from where camera problem comes, is it comes from kernel or is it comes from hal or is it comes from blob, it in most case comes from booth! No point working on something like that. instead I will try to fix stock kernel. Fixing 1.2.2 which was not stable kernel, no. Waiting for blobs forewer, no.

kholk & jerpelea, your kernel 1.3.3 is realy good in one point, but camera not, and its "not fixable" since nobody know if problem is related to kernel, or to hal, or to blobs, nobody want to waste time with it including me! You are great devs, you done a lot of work, everybody apreciate your work including me, but I not like sound which is started in this moment on this thread, I must go out, now, bye.

Edit:

I will not go out, I will continue \0/