To be honest, this might actually be a complete game changer… except Mozilla is over 80% “owned” by Google, so we’ll see… they might play ball…

What good is an OS if no one uses it 🤨. TempleOS is cool, but I bet you won’t find 100 people on earth that use it as a daily driver.

OK, I admit, I was looking into this a few years ago, so I don’t have the lastest info on this. Back then, drivers were the biggest problem. I had an Asus ZenFone 3 Max back then and I really wanted to try and run LineageOS on it. Turns out, everything works 🥳, except for RIL 😒. I could live without bluetooth or IR, that’s fine, but… this is a phone, it’s primary purpose is to make phone calls, not be a tablet. Hell, I could buy a $50 one if I really wanted a tablet.

My point is, there will always be obsticles and ways to overcome them. The only question is, is it worth my time and effort. A thing like ReVanced that takes 2 minutes to install, yeah, sure. But me doing backflips once every 2 or 3 months to overcome paying for things, nah, that’s just not worth it.

I stand behind this, there is no point in forking Android, you gain nothing. Simple apps that don’t need anything to run, yeah, those will run just fine, but as you mentioned, anything that involves data transfer to google services will be a hard to swallow pill. It’s just not worth it IMO. Better invest your time in a new platform. Sure it’s gonna be hard for it to take off, but hey, at least you’re not investing your time in a lost battle.

That may be true, but I’m sure the userbase is next to none.

That was never mentioned, it just said it had Google App compatiblity… and I didn’t look any further to be honest.

In my original reply, that’s why I said “almost no one”. Because, yes, some people might try and untangle that spaghetti code, riddled with tons of Google native things (there’s also LineageOS), but in reality, even if someone does it, no one is gonna use it. Sure, your oddball dev or Linux user, here and there, but mass adoption, no way. Main problem, as with every Android fork - drivers.

I really see no point actually forking Android if you can’t get a decent set of drivers that work, regardless if they’re closed or open source (though open source would be nice).

GrapheneOS is a privacy and security focused mobile OS with Android app compatibility…

That’s not the same as an ungoogled fork of Android, is it.

The monopolly argument will fall on it’s back in court once Mozilla’s finances come into question.

Oh, come on, he’s just a kid (2003), he’s just trying to figure things out 🤷… not everyone was born with a high EQ and even if they were, that doesn’t mean they developed it.

Not to mention it’s practically impossible to get rid of the Google code in it… Android is so deeply tied with Google, almost no one dares to tackle that code and degoogle it.

Of course, that’s not tye only project that does this, but they’re the only FOSS project, which is what you asked. xrecode can use it as well, but it’s not FOSS and l, once again, you have to provide the binary.

My mistake, I just remembered, MeGUI can use it as well (you have to provide the binary), which is a FOSS project as well.

That is why I was asking around… cuz I wanna clone it and make it FOSS, but it seems that no one has done that already, dispite the thing existing for about a decade now, for a reason.

As far as I’m aware of, the only FOSS project that has an option to use FDK-AAC is Handbrake, and they just let you point to the binary, that’s it… you have to compile it yourself.

I had a particular project in mind, I should have mentioned earlier, Fraunhoffer’s FDK-AAC. It’s open source, but the license is… tricky…

Then it’s not Open Source. So, which is it?

It is open source, you can find the source on GitHub and other git repos (their repos, not clones made by others).

The only midly-relevant question here becomes: did you use their source code to implement yours, or did you use public knowledge of the algorith etc (up to and including “white boarding”) to reimplement it?

Yes, I would use their source code as a reference, as in, study it and try to replicate what they have done, but in the process, deliberately doing things differently (sometimes it may be more efficient, other times it may not) so I would avoid legal consiquences.

Basically, their license says “Here’s the source, do whatever you want with it for your own personal use. You can not share binaries of it with anyone, individuals or companies. You can not use it for commercial use for free, you have to pay an implementation license. You can use our source to make sources for other OSes (their source is meant to be used in Android), but the same license has to apply to your implementation, and you can’t redistribute binaries, just the source.”

If you are selling cheese sandwiches, you can not sue “stolen profits” from someone who is selling bacon sandwiches just because their clients asked you for bacon sandwiches and you said no.

Basically, I’m giving away free bacon sandwiches, while the guy at the stand next to me is selling them. They’re not exactly the same, but the end result is the same, mine feed the people just as much as his do.

Mhm… OK, in that case, let’s say I reimplement Fraunhoffer’s FDK-AAC. It’s open source, but you can’t redistribute binaries of it, you can only compile it for your own personal needs and you can’t commercially use it for free. So, let’s say my reimplementation is licensed under BSD or GPL and I allow everything, even commercial use for free. That would cut on the profit Fraunhoffer is making from their product, but they can’t legally persue me because none of their code is in my reimplementation 🤨? That seems kinda off…

If it’s something better or different than your code, it’s a new thing.

They might steal the idea. Analyze the source, make some modifications regarding their needs, reimplement it in whatever language they like… that is still stealing, is it not?

no, the patent office would find your publication, deem it Prior Art and not grant the patent.

Yeah, but what if they completely rewrite the code, making it completely indistinguishable from yours. They could claim that they came up with the idea themselves 🤷.

Yeah, everyone could just snatch it, reimplement it and say it was their idea 🤷.

Though I use fish as well, this is some good info 👍.