And as usual, late here on the twitter account XD (but still better than never).
We wish you all a happy new year. 🥂🍾
Thanks for staying with us throughout the last year.
~Team PixelExperience.
We'll soon remove some Pie builds for devices that have already Q builds to make space on our storage for the 11 builds (no this isn't an April fools joke this time). Older devices that only have Pie builds will remain for some more time there in our download center.
Hey everyone :) Yep, this is us (no giveaways links in here for sure lol). We're maybe the last ROM project that created a twitter account after all that time, but meh, who cares? We're here now!
I have been always skeptical over the work done by
@EvolutionXROM
. They had nothing exclusive of their own, needless to say, their rom was "just another pickfest". They went to worst extents of picking from Havoc.
[1/2]Some people have been contacting/spamming us about the Zenfone Max Pro M1 (X00TD) applications, mainly the one by alexmercer09. We rejected him, due not fulfilling stuff that we've been, and still, requiring in the technical knowledge part...
[2/2] by the time he applied firstly. Continuing like that will only get the situation even worse for him, even more because of the historic that the X00TD community has, so please, just stop doing that.
@Sidbrahman
@IndiaPOCO
@xdadevelopers
So does all the other devices. We are going to release Plus Edition builds and March updates together. No ETAs or we will never answer ;-)
@thanosgreyjoy
1 - We aren't lying. We are humans and we have personal life too, stuff more important to attend. Custom ROM development is just a hobby of ours.
2 - Set the device as Pixel 4/4XL and manufacturer as Google on props and boom you get the GA 2.0.
@aabhasvermaaa
Unfortunately there's no one in the team with the device. If you'd really like to have PE for it, you can donate a device unit for someone of the core team or maintainers team. You check them out here:
@BasilBinu3
Though we have a CI/CD for our releases, there's still the need to the device's maintainer need to trigger the builds and test themselves. After all neither all core admins have all the 70+ devices being maintained right now.
@itssurpk
@realmemobiles
@realmecareIN
@MadhavSheth1
@LineageAndroid
From our end it's because we have no maintainer for the device in question. As such we won't provide builds for the device unless we have someone in our team with it + complying with our Code of Conduct and device requirements. ~HP
@landmiller18
None of the maintainers, neither core team members have a Deen (codename of the Motorola One). Unfortunately we can't do anything in that case.
@Soumyad24574236
Unfortunately we don't have a maintainer for the device, neither anyone in our team have the device (as far as we know). We understand the requests, but we won't do blind builds just because of the community requests to do a build for a device that no one in our team have. ~HP
@Ugy13132739
The point would be checking if the device codenames are the same, otherwise the recovery will stop immediately the flash either way as you aren't supposed to be flashing over joyuese a build that is made for curtana. ~HP
@Archit_Mishra_
We understand the requests, but we won't do blind builds just because of the community requests to do a build for a device that no one in our team have. ~HP [2/2]
@RameshP_1996
Unfortunately none of the team members have the device, neither plans of buying a unit. As per our Code of Conduct we can't simply make builds for any devices as we wish to. That's to avoid releasing builds without proper testing.
@SuvajitSingh4
@IndiaPOCO
@xdadevelopers
ATM we don't have any maintainer for the device, neither someone in the team with it. We won't do any sort of blind builds just as per users desire(s). ~HP
@shuklashailesh7
We don't have a maintainer for the device since December 2019. Without anyone of our team having the device, nothing can be done regarding it from our end. ^HP
@Archit_Mishra_
We do offer support for the Realme 5 Pro, however, if you meant any other Realme 5 but the 5 Pro, then unfortunately we don't have a maintainer for the device, neither anyone in our team have the device (as far as we know).[1/2]
@kzaneo
Unfortunately we don't have a maintainer for the device, neither anyone in our team have the device (as far as we know). We understand the requests, but we won't do blind builds just because of the community requests to do a build for a device that no one in our team have. ~HP
@supt69
Unfortunately we don't have a maintainer for the device, neither anyone in our team have the device (as far as we know). We understand the requests, but we won't do blind builds just because of the community requests to do a build for a device that no one in our team have. ~HP
@NilajBanerjee1
Unfortunately none of the team members have those devices. As per our Code of Conduct, with a goal of avoid shipping builds that might screw the users device in someway, the team members are required to have the device in hands.
@Prakash60499961
Unfortunately we don't have a maintainer for the device, neither anyone in our team have the device (as far as we know). We understand the requests, but we won't do blind builds just because of the community requests to do a build for a device that no one in our team have. ~HP
@chandravedant
The reason is simple. There's no maintainers for those devices. We don't allow blind builds without the device being on the maintainers hands (of course some devices may be possible to do so as per the devices are really close to each other. For example OP5/5T)
@tayfunturkmen_
We can't if there's lack of interest from the person who's building for apply for official status, neither we can guarantee that he'll be approved once he applies for the maintainship.
@mishu0507
Kudos for our Mi A3 maintainers nullbytepl and pqhaz for their work on the device side too. They did a great work on the device side :-) ^HP
@TwitterSupport
Thanks for suspending the impersonating Twitter account
@PixelExperience
. But can we get back the username as well? It would be really helpful.
@Kartik39794644
Sorry but that's not the case. But if you mean why there's no where versions marked as "Stable", it's simply because we stopped releasing Q builds starting from this month and eleven is yet to be considered stable for all devices (most of them are stable already) ~HP