raphael build reuploaded with MIUI FOD circle icon

Public statement regarding POCO F4 (munch) crowdfunding organized by Xiaomeme/POCO alliance federation

https://telegra.ph/Crowdfunding-Contract-with-DEV-and-Poco-Alliance-MUNCH-07-16 (archived version)

Premises:
I'm gonna be both honest and direct while I go through every step which surely needs some clarifications.
Also I'm sorry if this can be badly written or something, I'm on vacation, writing this with my phone, 100km away from my PC, having slept only 3 hours tonight.
Also, if you're not used to Xiaomi communities, I'm terribly sorry, this will look extremely cringe for you, and for me as well, but let's just say Xiaomi communities are special and needs some special treatments (that's the reason I decided to leave any public Xiaomi group)

Start:
Considering munch has a Qualcomm Snapdragon 870 (same SoC family as lmi, alioth and apollon) I decided to happily accept this crowdfunding to start development for this device, since it would have been easy enough for me.
Usually, a crowdfunding works like so:
- Developer propose for working for a device
- A public spreadsheet is made and managed by the developer where donations are tracked
- People donate money
- Developer buys the phone and does stuff for it
And any sort of developer-contributor relation should end there, without any time constraints, nor pretending anything
...but it isn't the case right here.

Xiaomeme federation (probably to avoid what happened with POCO F3 crowdfund and Vasi, which totally made a mess and didn't pull out anything useful in 1 (one) year) decided to make developers sign a sort of agreement in which they promise to do some stuff. Saying "some stuff" is definitely an understatement.

Let's go through them:
- 3 years support2 years support (it has been edited after pointing this out, not like it changed much)
Sheesh that's a lot of time, for instance, I got POCO F2 Pro with a self-managed crowdfund, and 2 years hasn't passed yet, but it feels like an eternity (still, I'm happily working on this device and no one complained, nor pretended stuff). The issue itself aren't the 2 years, it's the fact that they want to force me to work for a certain period of time, which is not a good thing, I'm not working for anyone, I just do this stuff for myself, thus making me feel like I'm doing this because I'm forced to is not fine to me.

- I'm gonna skip second, third, fourth and fifth point, probably because that's something I would definitely do without being forced to do it.

- Sixth point is related to first one

- Seventh point is a very hot take:
"In case community is not happy with devs work, he needs to return the device unconditionally."
What's the parameter for evaluating my work? ROM not booting? Bluetooth audio not working? PUBG lagging? Missing Dirac implementation? This definitely needs some clear up, and even if it was cleared up somehow, you should evaluate what I can and will do depending on my previous work with other devices (spoiler: I make sure everything works, no ricing or additional useless features). To end this point, I'm sure not everyone will be happy how I do stuff, so if one complains I have to return the device? Yeah, totally no sense.

- Gonna skip the following points except point number 10: Even if I were to sign the document, it wouldn't have legal meaning (at least here in Italy, since I live here), so just a friendly warning before someone thinks that I'm legally obligated to work on it.
Again, I would do it, but not because of the contract. Crowdfunds are based on trust.

Conclusions:
I'll say it again, a crowdfund is (and should be) a thing entirely organized by the community, without any external third party involved, based entirely on good faith between the two parts (developers and contributors). If this becomes like a contract, then it doesn't make sense anymore.
To sum it up, if they don't trust me, and instead they force me with this type of fake-contract, I'm gonna end this right here to protect my image, I'm sure sane people is thinking "wtf" when reading that Telegraph document, and I do that as well.

it's gonna be treated like a normal crowdfunding, then I'll be more than available to work on munch, until my unit dies (like I'm doing with my POCO F2 Pro, or POCO X3 Pro if that matters (again thanks POCO Italy for giving me that phone), or Mi 9T Pro (thanks again to @MaxBear for entirely paying the phone price and sending it to me))
These are the kind of gestures from the community that I appreciate and gets me going with what I do, but oh boy being so enforced is a no-no for me.
Once Xiaomeme will propose something saner to me, I'll happily accept, but until then, it's a no.

Hi everyone,
As you might imagine, keeping up with all these devices takes away a lot of my free time and money, so if you appreciate my work it would be awesome if you could donate something, even 5$ are fine.

PayPal: paypal.me/sbarezzi
GitHub Sponsors: github.com/sponsors/SebaUbuntu
Buy Me a Coffee: buymeacoffee.com/sebaubuntu
Patreon: patreon.com/sebaubuntu (highly not recommended, just make one-time donations if you want to donate)

Always fun seeing people brag about booting AOSP at every Android release cycle lol
With that being said, I'll start working on Android 13 when I want to, so, friendly warning, don't even try to ask about ETA about anything

First 19.1 build for Xiaomi Mi 9 SE (grus) is gonna be out tomorrow, it's not gonna be dirty flashable from unofficial releases do to FBEv1
Plus I switched to retrofit dynamic partitions, so be sure to follow LineageOS wiki instructions and to only use Lineage Recovery

twrpdtgen v3 is out
This release marks the completion of the unification of twrpdtgen with aospdtgen, now sharing most of the code in a shared library (libandroid), bringing down the LOC number to less than 100 (excluding templates)
This update also brings support for AVBv2, dynamic partitions, system as root, better architecture detection, etc.
If you find regressions or new issues you can report them here

Thanks a lot to The LineageOS Project ♥

Hi everyone,
First of all, Merry Christmas!

Second: the kernel that will be used on LineageOS 20 for alioth, apollon and lmi has support for all the currenly released Xiaomi SM8250 devices, so if you have one of the following devices and you wish to maintain LineageOS for it or you know someone that is willing to do it, contact me, I can help if needed:
Mi 10 Ultra (cas), Mi 10 Pro (cmi), Xiaomi Pad 5 Pro 12.4 (dagu), Xiaomi Pad 5 Pro Wi-Fi (elish), Xiaomi Pad 5 Pro 5G (enuma), Redmi K40S / POCO F4 (munch), Xiaomi 12X (psyche), Mi 10S (thyme), Mi 10 (umi)

Similar situation will happen with Xiaomi SM8150, support for cepheus and raphael is already planned, but the following devices will have support in the kernel sources and are currently waiting for a maintainer:
Mi MIX 3 5G (andromeda), Mi 9 Pro 5G (crux), Xiaomi Pad 5 (nabu)

This is also the case for Mi CC 9 Meitu Edition (vela), basically everything is ready for it (also on the common tree)

Feel free to contact me in my group (@SebaUbuntuChat) or in private (@SebaUbuntu)

Changelog 27 - Thriving Thirteen, Amazing Aperture, Careful Commonization

https://lineageos.org/Changelog-27/

#grus #t
LineageOS 20.0 for Xiaomi Mi 9 SE (grus)

Build date: 2023/01/01
Download: Here
Device wiki page: Here
Installation instructions: Here

@lineageos_updates

I've started moving from barezzisebastiano@gmail.com to seba@sebaubuntu.dev, please contact me on this email if needed
For anyone that cares about this stuff (tinfoil users?): since I'll commit Git changes with this email address, my public GPG key has been updated to reflect this change, you can find it here or here

Announcing @lineageos_updates_bot, a bot that you can use or add to groups to get the latest update for a device or find out when the next build will happen

Made a new app https://github.com/SebaUbuntu/Athena
It's still WIP, feedback/new ideas are accepted

Due to several changes in LineageOS updater's API, the bot misbehaved for a few days with some features like builds checking.
Both the library and the Telegram bot have been adapted for the new v2 updater API, from now on the builds posted here will include some additonal informations, one of them being direct links to the build's files.
The bot will also be more responsive when using commands

#lmi #t
LineageOS 20.0 for Xiaomi POCO F2 Pro / Redmi K30 Pro / Redmi K30 Pro Zoom Edition (lmi)

Device informations: Here
Installation instructions: Here

Date: 2023-03-25
Download: lineage-20.0-20230325-nightly-lmi-signed.zip (1.3 GB)

Additional files:
boot.img (134.2 MB)
dtbo.img (33.6 MB)
recovery.img (134.2 MB)
super_empty.img (4.6 kB)
vbmeta.img (8.2 kB)

@lineageos_updates

Meh broken link, https://mirrorbits.lineageos.org/full/lmi/20230325/lineage-20.0-20230325-nightly-lmi-signed.zip