Sony Open Device Support for Mediatek SOC about device-sony-common

[jerpelea]

since MTK is not included in this program I can't promise anything

[ix5]

Duplicate of #777 (comment)

Whether or not the blame lies with Sony, you know when buying a MTK device you're gonna have a bad time developing. Start a petition, write to the CEO, whatever, ranting on the bug tracker won't do your cause much good.

[bigrammy]

"when buying a MTK device you're gonna have a bad time developing"
Why would that be please explain?
Team MAD didn't find it too difficult but maybe they were real devs unlike some who simply call make and wait for it to compile. Not aimed at you but the mediatek haters who just pretend to be dev's and have no real idea but feel it's OK to say it because they read some old blog post from 6 years ago.
I can give you all the source code you like the problem lays with Sony as I said and since I can see no FORMAL way to ask for support Ranting seems logical
It's help we want not a argument about misinformed pre conceptions about MediaTek.
It's OEM's who mess things up installing preloaders and lk's that block the RIL from working not Mediatek.
If there is a way to work with the Sony stuff then let us know how. Team MAD had Android 9 running on devices released with Android 6

SONY_S1_SUPPORT = yes
SONY_ONESW_MULTI_SIM_SUPPORT = yes
ARIMA_SMARTCARDSERVICE=yes

[jmpfbmx]

I think the same as @bigrammy he has the reason
We have been working hardly on the XPERIA L1, you can see our work at github.com/PineDevelopment
And we couldn't fix RIL, all MTK SONY Devices has the same err.
So if were supported by SODP all would be easier for us.
We can provide all you want.
If SONY don't use .sin format we will can flash by SP Flash Tool and we could build ALPS and upstream easier but no we can't
So pls consider our petition.
And pls @ix5 explain to me: "when buying a MTK device you're gonna have a bad time developing"this too
Thanks.
Regards,
Jose

[Paulbouchara]

I think the same as @bigrammy he has the reason
We have been working hardly on the XPERIA L1, you can see our work at github.com/PineDevelopment
And we couldn't fix RIL, all MTK SONY Devices has the same err.
So if were supported by SODP all would be easier for us.
We can provide all you want.
If SONY don't use .sin format we will can flash by SP Flash Tool and we could build ALPS and upstream easier but no we can't
So pls consider our petition.
And pls @ix5 explain to me: "when buying a MTK device you're gonna have a bad time developing"this too
Thanks.
Regards,
Jose

Regarding .sin you can always convert those to standard .img or whatever the tool uses to flash images
Other than that, as we already discussed for RIL there might be some telephony injection or special magic that relies on modem-switcher that seems different than our qcom based handling

[ix5]

Open Devices is working with the support of the OEM (Sony) and the BSP provider (Qualcomm), not against them as most MTK ports are.
It's great that you guys are such self-described "great hackers", but the simple fact is that MTK devices are shipped on very tight margins and as such, OEMs are quite wary of offering developer incentives such as BLU or are quite late with kernel releases.

I'm sure @jerpelea (who had to fight very hard to get the Qcom-based devices to where they are now) can try to escalate your issues with corpo people, but since the situation is as ever with low-end phones, I'm giving it little chances.

EDIT: Also, please use the bug tracker instead.

[jmpfbmx]

@Paulbouchara yes i know that we can convert .sin into .img but we can't flash with SP Flash Tool that is one of our problems.
And about RIL yes, i tried what we discussed but didn't work.
I have tried even to use some stock apps that contains RIL things and nothing.
IDK what happens with it but we couldn't make it work :(

[bigrammy]

EDIT: Also, please use the bug tracker instead.

I am not having a go at this project what you guys have done is nothing short of a miracle. I think sony make some great devices and i have the m5, c4, xa, xa1 and L1 (all MediaTek) I have held off buying the L3 and L4 because of the reasons stated and I ended up buying a Xiaomi Redmi Note 8 Pro (Begonia)(MTK) instead because Xiaomi release the kernel sources so there is some pretty active development going on.
If @jerpelea could bump us up the sony agenda that would be great.
If he would get one of these devices in his hands then that would be great.
Why not grab one then take a look then give us your thoughts. If it's not going to happen I will abandon Sony MTK Devices as others have.
Picking up a used Sony MTK used will cost very little but if anyone is struggling with the finances I have a spare one here.
I am unsure if any of the M.A.D Team like @fire855 have any interest or Sony experience but if anyone knows MediaTek best it would be one of those guys so some input from @fire855 & or @DerTeufel would be just Great.

[jerpelea]

@bigrammy
For the moment we are supporting only QCOM devices

[bigrammy]

@jerpelea

Understood but please be sure to let us know if anything changes with regard to MTK support.
If any Info about what Sony do with regard to the RIL and SIM detection on these MediaTek devices becomes available then please let us know. Maybe you could ask on our behalf since we have everything else working on these devices. :(