Indeed, this looks interesting. I'm wondering if LineageOS devs already made use of it. So far, there is no official support for these devices.

It looks complete, but unfortunately, code for blobs is still proprietary and marked as confidential. I'm sure the dev who published the code doesn't have the permission from Qualcomm and other suppliers to do this and I'm really surprised that it hasn't been taken down yet.
Publishing proprietary and confidential code usually hurts a clean reverse-engineering effort, because a future contributor could then have copied non-free code which would be copyright infringement. For some interesting parts, like TrustZone, blobs are directly committed and no source is available. But there seems to be some documentation which could be helpful.

I hope that there is some free code in there that wasn't yet available. Such code could be helpful not only to port Replicant to these devices, but also to many other devices.

Wolfgang Wiedmeyer wrote:

It looks complete, but unfortunately, code for blobs is still proprietary and marked as confidential. I'm sure the dev who published the code doesn't have the permission from Qualcomm and other suppliers to do this and I'm really surprised that it hasn't been taken down yet.

Once it is published, it will make more and more noise if they make some efforts to shut it down.

Publishing proprietary and confidential code usually hurts a clean reverse-engineering effort, because a future contributor could then have copied non-free code which would be copyright infringement. For some interesting parts, like TrustZone, blobs are directly committed and no source is available. But there seems to be some documentation which could be helpful.

It should be very interesting to have access to information for interoperability, even if each developer should be cautious and not copy anything without the license of course.

I hope that there is some free code in there that wasn't yet available. Such code could be helpful not only to port Replicant to these devices, but also to many other devices.

Hope so.

Fil Lupin wrote:

Wolfgang Wiedmeyer wrote:

Publishing proprietary and confidential code usually hurts a clean reverse-engineering effort, because a future contributor could then have copied non-free code which would be copyright infringement. For some interesting parts, like TrustZone, blobs are directly committed and no source is available. But there seems to be some documentation which could be helpful.

It should be very interesting to have access to information for interoperability, even if each developer should be cautious and not copy anything without the license of course.

That's false. The interoperability exception to copyright applies to clean-room reverse-engineering; it does not apply to code written based on information obtained from looking at pirated code. Pirated documentation is a grayer area, but I'd still recommend avoiding it. (The usual disclaimer applies: I'm not a lawyer, and my understanding is based on U.S. law; laws might be different in your jurisdiction.)

IUNI leaked even more proprietary source on their announcement here: https://forum.xda-developers.com/android/software/official-iuni-announcement-freeing-t3652352

They left a base64 encrypted message at the end with many other links:

WWVzLCB5ZXMsIHdlIGhhdmUgcHJvbWlzZWQgeW91IGEgYm9udX MgaW4gYWRkaXRpb24gdG8gdGhlIHN1cnByaXNlIGFuZCBoZXJl IGl0IGlzOgoKClRDTC1BbGNhdGVsIDoKCgpBbmRyb2lkIFBhcn QgMS0yIDogaHR0cHM6Ly9naXRsYWIuY29tL3RjbC5wcm9wcmll dGFyeS9hbGNhdGVsLWFuZHJvaWQtcGFydF8xCkFuZHJvaWQgUG FydCAyLTIgOiBodHRwczovL2dpdGxhYi5jb20vdGNsLnByb3By aWV0YXJ5L2FsY2F0ZWwtYW5kcm9pZC1wYXJ0XzIKCk1vbnN0ZX JPUyA6IGh0dHBzOi8vZ2l0bGFiLmNvbS90Y2wucHJvcHJpZXRh cnkvbW9uc3RlcgoKRG9jdW1lbnRhdGlvbnMgOiBodHRwczovL2 dpdGxhYi5jb20vdGNsLnByb3ByaWV0YXJ5L2RvY3VtZW50YXRp b25zCgoKCk1pY3JvbWF4IDoKCgpZdSBZdXJla2EgMiA6IGh0dH BzOi8vZ2l0bGFiLmNvbS9taWNyb21heC5wcm9wcmlldGFyeS95 dS15dXJla2EtMgoKCgpQcm90cnVseSA6CgoKVjEwIDogaHR0cH M6Ly9naXRsYWIuY29tL3Byb3RydWx5L3YxMAoKSHVtbWluZ0Jp cmQgOiBodHRwczovL2dpdGxhYi5jb20vcHJvdHJ1bHkvaHVtbW luZ2JpcmQ=

Decoded=

Yes, yes, we have promised you a bonus in addition to the surprise and here it is:

TCL-Alcatel :

Android Part 1-2 : https://gitlab.com/tcl.proprietary/alcatel-android-part_1
Android Part 2-2 : https://gitlab.com/tcl.proprietary/alcatel-android-part_2

MonsterOS : https://gitlab.com/tcl.proprietary/monster

Documentations : https://gitlab.com/tcl.proprietary/documentations

Micromax :

Yu Yureka 2 : https://gitlab.com/micromax.proprietary/yu-yureka-2

Protruly :

V10 : https://gitlab.com/protruly/v10

HummingBird : https://gitlab.com/protruly/hummingbird

I've edited the topic name just to warn people.

I'm not a legal expert but taking a look at the source code may compromise the ability of the people who do to work on Replicant!

Here are more details on the topic: https://libv.livejournal.com/26972.html
There is also some more legal background on the necessary conditions to enable leaked source code to be used as documentation in the OsmocomBB wiki: https://osmocom.org/projects/baseband/wiki/LegalAspects

So it might be a good idea to consult a lawyer before looking at the source.
If what's inside might be interesting, we could as the FSF for advises on the topic as they have lawyers.
The FSF might also have a better understanding of what's going between the software freedom law center (that gives pro bono legal advises in cases like that) and the software convervancy, to understand if we can still trust the software freedom law center to give us legal advises.

(Edited for completness)

Denis.

I've added a warning on top, just to warn people of the potential issues.
I've tried to warn wile still being the less intrusive possible and not touch Mariusz Suchodolski's text to preserve freedom of speech.

Feel free to suggest a better way to do it if you find one.

Denis.