#PE #ROM #OFFICIAL #10
Pixel Experience - OFFICIAL | Android 10
Updated: 24/11/2019
Mod Edit : Links removed.
Device Changes: -
- Enabled volte for Airtel/Vodafone ( Might need a wipe still not 100% if works )
- Nuked custom sf offsets
- Imported some missing radio blobs
- Enabled use_data_netmgrd
Rom changes:
- IMS Changes ( viLTE shoud work fine now )
Isn't this the same build as the other official PE ?
Well, you aren't the official maintainer. Why are you reposting builds of Dyneteve?
Thug dev
Mod Edit
2 Threads on same topic is not allowed and there is already an Official PE is released by maintainer here
May I remind you XDA Forum Rules #12
12. Sharing
XDA-Developers is based on the principle of sharing to transmit knowledge. This is the cornerstone of our site. Our members and developers freely share their experience, knowledge, and finished works with the rest of the community to promote growth within the developer community, and to encourage those still learning to become better. There are those, however, who take advantage of this model and try to make personal gains from the hard work of others.
In order to preserve the delicate balance between sharing for the good of the community and blatant self-promotion, regular members and developers alike must understand (and agree) to the following:
12.1. Give credits where due - Credits and acknowledgements for using and releasing work which is based on someone else's work are an absolute must. Works reported to have no credits will be taken down until proper acknowledgements are added by the member in question;
12.2. Courtesy - While most of the work released on our site falls under the umbrella of open source, that is not the only license model being used by developers on xda-developers. In order to prevent problems, we ask that if you decide to base your work on someone else's that you check the license model being used (as it might not be as permissive as one may think);
12.3. Re-releasing other's works as your own is forbidden. The code that you release into the wild must have something beyond minor aesthetic changes that makes it better than the last. As this can be subjective, kang reports will be reviewed on a case by case basis. If you feel that your code has been kanged, please contact the Dev Relations team (listed below) if you cannot solve the issue amicably via PM. Please understand that you will be asked to provide evidence to substantiate your claim;
12.4. Developers can issue take down requests (by contacting the Dev Relations team) under the following circumstances:
- in-process builds start showing up on forums when the developer is not yet ready to release the work;
- cases in which another developer is too aggressively soliciting donations or misrepresenting the work (kanging);
- unofficial builds where an official build is already available;
Thread Closed.
jackeagle
Forum Moderator
Related
Everyone working with GPLed code, in our case the Linux kernel which is under the GPLv2, needs to understand how the licence affects them, and the work they put out on XDA developers, to aid understanding a good write up of this issues has gone up on the portal, you can read it here;
XDA-Developers and the GPL
GPL compliance is taken very seriously on XDA, but at the same time I remind people to report anything via the proper channels rather than confronting anyone in public, which always does more harm than good.
A note to ROM developers:
Using a non GPL compliant kernel makes your ROM non compliant and subject to removal.
If you are using another developers kernel, linking to that kernels thread will make you GPL compliant (assuming that the kernel in question is compliant)
Originally written by Veyka
Since we got reports about ROM threads missing the kernel sources I'd like to ask ALL ROM Chefs and Kernel Hackers to review their threads and introduce the change accordingly.
When you use the kernel of a certain project (AOSP, AOKP, CM, ParanoidAndroid, PACMAN, ...) you have to provide a link to the GitHub repository of the project where the kernel sources you used can be found. In case you introduced changes to the kernel source, you are required to published them as well. Giving proper credits is also expected (to the project from where you took the kernel and to the developer/s of each modification you may have used (i.e. CPU Governors)).
When you created your "own" kernel (i.e. backported from one of the projects mentioned above) you have to provide the kernel sources plus all modifications you introduced to it. Again, giving proper credits to the project from where you took the kernel source and crediting the developer/s of the modification/s you may have used is expected.
Threads failing to comply with this rule will be closed and the OP be asked to comply or have the thread perma locked for failing to comply with the terms of the GNU General Public License.
In short: You do not have to publish the sources of your ROM (NOT applicable to Recognized Developers - you have to provide buildable sources of the ROM as well) if you don't intend to (though we rather see you being a valuable part of the OpenSource community by sharing your sources), however, you HAVE to publish, or link-back, to the kernel source!
This is not up for discussion.
Everyone working with GPLed code, in our case the Linux kernel which is under the GPLv2, needs to understand how the licence affects them, and the work they put out on XDA developers, to aid understanding a good write up of this issues has gone up on the portal, you can read it here;
XDA-Developers and the GPL
GPL compliance is taken very seriously on XDA, but at the same time I remind people to report anything via the proper channels rather than confronting anyone in public, which always does more harm than good.
A note to ROM developers:
Using a non GPL compliant kernel makes your ROM non compliant and subject to removal.
If you are using another developers kernel, linking to that kernels thread will make you GPL compliant (assuming that the kernel in question is compliant)
Originally written by Veyka
Since we got reports about ROM threads missing the kernel sources I'd like to ask ALL ROM Chefs and Kernel Hackers to review their threads and introduce the change accordingly.
When you use the kernel of a certain project (AOSP, AOKP, CM, ParanoidAndroid, PACMAN, ...) you have to provide a link to the GitHub repository of the project where the kernel sources you used can be found. In case you introduced changes to the kernel source, you are required to published them as well. Giving proper credits is also expected (to the project from where you took the kernel and to the developer/s of each modification you may have used (i.e. CPU Governors)).
When you created your "own" kernel (i.e. backported from one of the projects mentioned above) you have to provide the kernel sources plus all modifications you introduced to it. Again, giving proper credits to the project from where you took the kernel source and crediting the developer/s of the modification/s you may have used is expected.
Threads failing to comply with this rule will be closed and the OP be asked to comply or have the thread perma locked for failing to comply with the terms of the GNU General Public License.
In short: You do not have to publish the sources of your ROM (NOT applicable to Recognized Developers - you have to provide buildable sources of the ROM as well) if you don't intend to (though we rather see you being a valuable part of the OpenSource community by sharing your sources), however, you HAVE to publish, or link-back, to the kernel source!
This is not up for discussion.
Mod Edit: redacted name with XXXXXXXXXX
I was the first developer to make MIUI8/9 for X52X，I spend a lot of time perfecting，but XXXXXXXXXXXXXXX theft of my port way， did not specify the source, I am very angry, I hope everyone know.
I taught him how to port MIUI, and i give him port way，but him return kindness with ingratitude evil for good
now，I warned SagarMakhar to stop releasing MIUI for X52X，
I've warned XXXXXXXXXXXXXX several times, please don't be a thief，
If you respect me, please indicate the source.
If you don't believe me,You can use Beyond Compare 3 to compare checks.
I want everyone to respect copyright and not steal other people's achievements.
Thank you for your support and understanding
* * * Thread Closed * * *
#1 this thread is in the OTHER DEVELOPMENT section, there is no development going on, only discussion.
#2 There is a proper way to report someone who you think is improperly using your work, or used work with no credit, etc, and blasting it in a development thread is NOT the proper way. The original author needs to REPORT the offending user and document their original work, dates, checks, sources, etc.
Hi everyone!
Just wanted everyone to know that
Team_Astr4y4L Is looking for Beta Testers for several ongoing development projects, including a project aimed at providing a remote FRP bypass service for LG devices !
UPDATE:
the team is having trouble with the dmvarity on the newer builds of android...
Confirmed working for zone3 K4-k121
Believed working for all lollipop roms that are not encrypted,
more testing is needed, and a better means of bypasing or disabling dm-varity with out modifying /boot
FOR NOW WE ARE LOOKING FOR MORE LOLLIPOP DEVICES TO TEST thanks,
The service is hosted at Team_Astr4y4L's website and we are working to extend the service to encompass a larger selection of devices.
For that Purpose We are offering people a chance to be a beta-tester and be one of the first to use the service for Thair particular device.
As I said there are several other projects going into Beta-Test also so if your interested check it out.
A lot of these projects will cost money once the devices and service are considered Proven Stable and working
As a beta tester you get in absolutely free of charge
To Participate you must fill out the beta test request form at our website and if your device isn't supported yet, you're almost guaranteed to get a spot on the crew.
This Thread will be kind of a Support thread for the FRP beta testers and a place to ask questions about the project
here's the link to become a beta tester,
MOD Edit :- Links Removed
I hope this will be mutually helpful for the project and also the Users out there that have run out of options with their FRP locked device
Thanks,
Astr4y4L
Team_Astr4y4L
Hello. I have an LG Aristo (ms210) with September 2017 Security. Is there anyway to bypass frp on it? It is MetroPC with Tmobile but it doesnt running Tmobile anymore, I think.
Thread closed as offsite invitation and there is no beta program available on the link shared as of now.
Thanks
XDA Staff.
Hi Guys I just saw couple of android 8.1 test builds or alpha builds for our P2 in Android File Host website. In which the few Rom available in AFH are not mentioned or thread is not created in XDA] so that I'm just sharing it with you!
Checkout the source below to stay updated.
Source
mod edit - link removed
Edit - Few download links removed cuz they are not my work & I'm not interested in sharing it anymore.
Disclaimer:
# If you don't want to share your work, then don't share it in public.
# I'm not responsible for any Damage, Proceed at your own risk.
Is volte enabled in any of them?
I'll give a shot at the Pixel Experience ROM...Its 757mb!!
Let's see what features it holds..
I'll report back after using it
rohit1512 said:
Is volte enabled in any of them?
Click to expand...
Click to collapse
I can't tell cuz I'm not using such a carrier.
ASP02 said:
I'll give a shot at the Pixel Experience ROM...Its 757mb!!
Let's see what features it holds..
I'll report back after using it
Click to expand...
Click to collapse
Haha, have fun
Forum Rules
12. Sharing
XDA-Developers is based on the principle of sharing to transmit knowledge. This is the cornerstone of our site. Our members and developers freely share their experience, knowledge, and finished works with the rest of the community to promote growth within the developer community, and to encourage those still learning to become better. There are those, however, who take advantage of this model and try to make personal gains from the hard work of others.
In order to preserve the delicate balance between sharing for the good of the community and blatant self-promotion, regular members and developers alike must understand (and agree) to the following:
12.1. Give credits where due - Credits and acknowledgements for using and releasing work which is based on someone else's work are an absolute must. Works reported to have no credits will be taken down until proper acknowledgements are added by the member in question;
12.2. Courtesy - While most of the work released on our site falls under the umbrella of open source, that is not the only license model being used by developers on xda-developers. In order to prevent problems, we ask that if you decide to base your work on someone else's that you check the license model being used (as it might not be as permissive as one may think);
12.3. Re-releasing other's works as your own is forbidden. The code that you release into the wild must have something beyond minor aesthetic changes that makes it better than the last. As this can be subjective, kang reports will be reviewed on a case by case basis. If you feel that your code has been kanged, please contact the Dev Relations team (listed below) if you cannot solve the issue amicably via PM. Please understand that you will be asked to provide evidence to substantiate your claim;
12.4. Developers can issue take down requests (by contacting the Dev Relations team) under the following circumstances:
- in-process builds start showing up on forums when the developer is not yet ready to release the work;
- cases in which another developer is too aggressively soliciting donations or misrepresenting the work (kanging);
- unofficial builds where an official build is already available;
In summary, we want people to have access to work and knowledge alike. Sharing is good and courtesy and ethics go a long way.
Developers with questions, comments, complaints, or concerns about our rules (or anything!) should send a PM to our Dev Relations team (efrant or sykopompos) or to a Moderator. We are here to help!
Click to expand...
Click to collapse
thread closed and ... cleaned