Develop Bugs

Looking for a Dev to maintain for PAC-man Rom

{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Hello,
I am one of the admin for PAC-man Roms. We are expanding and are looking for a maintainer for this device. Currently we build for 120+ devices. What we are looking for is a dev that will be able to add support, support their thread, join us in our hangouts, and possible dev for pac by adding new and innovative features,
What we offer
Maintainer
We offer nightlies built by our build farm, help with adding support for your device, entrance into the maintainer hangout, hosting of your roms on our host server with a download counter, and a hell of a lot of fun.
Developer
We offer a dev only build server to test new features, interactions with our 2 donzen developers, and entrance into our dev hangout.
Webdesign
We offer access to our website via ftp access and open offers to adding new features and funtionality to the website, and access to our web team hangout
Graphics Team
We offer access to the different image galleries and wallpaper repositories. Ability to add your works to our threads, website, and wallpaper apk, and access to our graphics team hangout
Requierments
Maintainer
Please have knowledge of github, some gerrit, and some knowledge in adding support for devices. Have released aosp compiled by you builds is a must.
All devices will be using cm repos and theMuppets repos for these devices.
Developer
Please submit a new feature/updates/apk/etc to our gerrit.
Webdesign
Please send me links of some of your websites. Looking for html, css, and/or php, and/or javascript
Graphics Team
Please send me links of graphic,banners, sigs, wallpapers, etc.
WEBSITES​
Code:
* [URL="http://pac-rom.com/index.html"]PAC-Rom site[/URL]
* [URL="http://forum.pac-rom.com/"]PAC Forum[/URL]
* [URL="http://review.pac-rom.com/"]PAC Gerrit[/URL]
* [URL="https://github.com/PAC-man"]PAC Github[/URL]
* [URL="http://stats.pac-rom.com/stats"]PAC Stats[/URL]
* [URL="https://plus.google.com/102557242936341392082/posts"]PAC Google+[/URL]
* [URL="https://www.facebook.com/PacManTheAioRom"]PAC Facebook[/URL]
* [URL="https://twitter.com/PACmanROM"]PAC Twitter[/URL]
I look forward to hearing from you.
Please PM me first then you can gtalk/hangout me
my gtalk/hangouts is [email protected]

I can't help you since I'm not a developer, but I hope you do find someone. It would be awesome to have someone help mantain official PAC in our device =)

I thought we have already an official man for Pac. @faust93
Think he's the best man for that job.

cyraxx84 said:
I thought we have already an official man for Pac. @faust93
Think he's the best man for that job.
Click to expand...
Click to collapse
Nope not on any of my lists or hangouts but if he's willing he's more than welcome to join.
XDA Moderator

Papa Smurf151 said:
Nope not on any of my lists or hangouts but if he's willing he's more than welcome to join.
XDA Moderator
Click to expand...
Click to collapse
Oh really?? Then it was a dream..
https://github.com/PAC-man/android_vendor_pac/blob/cm-10.1/CONTRIBUTORS.mkdn | grep faust93

faust93 said:
Oh really?? Then it was a dream..
https://github.com/PAC-man/android_vendor_pac/blob/cm-10.1/CONTRIBUTORS.mkdn | grep faust93
Click to expand...
Click to collapse
Lol where the hell did that come from lol... I was looking at 10.2 branch. Please hit me up on hangouts and ill close this thread. Sorry man my bad
XDA Moderator

faust93 said:
Oh really?? Then it was a dream..
https://github.com/PAC-man/android_vendor_pac/blob/cm-10.1/CONTRIBUTORS.mkdn | grep faust93
Click to expand...
Click to collapse
oh damn faust93 know that this could be may change! :laugh:

Thread closed at OP's request...

Looking for a Dev to maintain for PAC-man Rom

{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Hello,
I am one of the admin for PAC-man Roms. We are expanding and are looking for a maintainer for this device. Currently we build for 120+ devices. What we are looking for is a dev that will be able to add support, support their thread, join us in our hangouts, and possible dev for pac by adding new and innovative features,
What we offer
Maintainer
We offer nightlies built by our build farm, help with adding support for your device, entrance into the maintainer hangout, hosting of your roms on our host server with a download counter, and a hell of a lot of fun.
Developer
We offer a dev only build server to test new features, interactions with our 2 donzen developers, and entrance into our dev hangout.
Webdesign
We offer access to our website via ftp access and open offers to adding new features and funtionality to the website, and access to our web team hangout
Graphics Team
We offer access to the different image galleries and wallpaper repositories. Ability to add your works to our threads, website, and wallpaper apk, and access to our graphics team hangout
Requierments
Maintainer
Please have knowledge of github, some gerrit, and some knowledge in adding support for devices. Have released aosp compiled by you builds is a must.
All devices will be using cm repos and theMuppets repos for these devices.
Developer
Please submit a new feature/updates/apk/etc to our gerrit.
Webdesign
Please send me links of some of your websites. Looking for html, css, and/or php, and/or javascript
Graphics Team
Please send me links of graphic,banners, sigs, wallpapers, etc.
WEBSITES​
Code:
* [URL="http://pac-rom.com/index.html"]PAC-Rom site[/URL]
* [URL="http://forum.pac-rom.com/"]PAC Forum[/URL]
* [URL="http://review.pac-rom.com/"]PAC Gerrit[/URL]
* [URL="https://github.com/PAC-man"]PAC Github[/URL]
* [URL="http://stats.pac-rom.com/stats"]PAC Stats[/URL]
* [URL="https://plus.google.com/102557242936341392082/posts"]PAC Google+[/URL]
* [URL="https://www.facebook.com/PacManTheAioRom"]PAC Facebook[/URL]
* [URL="https://twitter.com/PACmanROM"]PAC Twitter[/URL]
I look forward to hearing from you.
Please PM me first then you can gtalk/hangout me
my gtalk/hangouts is [email protected]

Come on guys no one's interested?

bkjolly said:
Come on guys no one's interested?
Click to expand...
Click to collapse
I took it up and is gonna maintain for maguro

-Jesco- said:
I took it up and is gonna maintain for maguro
Click to expand...
Click to collapse
yes and glad you could join us. But this thread is looking for someone from the galaxy nexus to maintain the device

Deleted.
a manta sent this.

[Mandatory] XDA-Developers and the GPL

XDA-DEVELOPERS AND THE GPL
Hello Everyone,
As many of you know, here at XDA we have strict policy regarding GPL v2. What you may not understand is what that means and what effects it may have on you. Simply put "The GNU GPL is a software license agreement, under which parts of the Android operating system are licensed. The majority of Android is licensed under the Apache license, but the Linux Kernel (which is present in every running Android ROM in some shape or form) is licensed under the GPL (version 2)".
So what does this mean for the average user?
To keep things simple, this license is one of the reasons Android exists in the open source capacity that it does. It requires developers to keep their kernel source open and has created the community sharing programs that have made Android so wonderful.
If you are a developer what does this mean for you?
It doesn't matter if you are creating a whole rom or just the kernel, the process of being GPL compliant is a very simple one to explain. Basically, we expect you to either link the source that you have chosen to use or upload the source you have created into a format that can be viewed by everyone and anyone. Below are the 3 most common situations that developers run into when needing to stay GPL compliant under XDA rules.
1. If you are using a stock kernel you MUST mention where you obtained your source. Also, having a link leading to where the manufacture has uploaded their source is always helpful.
2. If you are using a community driven source build (e.g. CyanogenMod, AOSP, or Parandroid) or a singular developer's source you MUST link directly to the repository that contains the kernel for that specific device. If you are only linking to another thread or to a general repository, this will not be considered as being GPL compliant unless the code has not been modified.
3. If you are forking a repository that is similar to the examples listed above in #2, you MUST publish and link your entire kernel source. This includes any and all changes that you have made. Two of the most common ways developers publish their source on XDA is either with Gerrit, or GitHub. While these two methods are recommend, they are not the only routes you can choose to accomplish this. All that is required is that the source can be viewed and downloaded by anyone who wishes to do so. When releasing an update, your repository must be updated the moment you release your kernel on XDA. If you can post your update to XDA, there should be no reason as to why you cannot release your source.
What if the manufacture for my device has not released their kernel source?
In a perfect world this would not happen but unfortunately this is not the case. Pulser-G2 recently wrote a portal article explaining a certain situation that has come across our desks.
With all of that being said I will leave you with this...
By posting your work on XDA-Developers, you are agreeing that it complies with relevant licensing conditions. As such, by posting a kernel or other work containing GPL code, you are confirming to us that you have made this source code available publicly under the GPL. Failure to follow this policy will result in the closure of your thread and the removal of the download links.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}

[Mandatory] XDA-Developers and the GPL

XDA-DEVELOPERS AND THE GPL
Hello Everyone,
As many of you know, here at XDA we have strict policy regarding GPL v2. What you may not understand is what that means and what effects it may have on you. Simply put "The GNU GPL is a software license agreement, under which parts of the Android operating system are licensed. The majority of Android is licensed under the Apache license, but the Linux Kernel (which is present in every running Android ROM in some shape or form) is licensed under the GPL (version 2)".
So what does this mean for the average user?
To keep things simple, this license is one of the reasons Android exists in the open source capacity that it does. It requires developers to keep their kernel source open and has created the community sharing programs that have made Android so wonderful.
If you are a developer what does this mean for you?
It doesn't matter if you are creating a whole rom or just the kernel, the process of being GPL compliant is a very simple one to explain. Basically, we expect you to either link the source that you have chosen to use or upload the source you have created into a format that can be viewed by everyone and anyone. Below are the 3 most common situations that developers run into when needing to stay GPL compliant under XDA rules.
1. If you are using a stock kernel you MUST mention where you obtained your source. Also, having a link leading to where the manufacture has uploaded their source is always helpful.
2. If you are using a community driven source build (e.g. CyanogenMod, AOSP, or Parandroid) or a singular developer's source you MUST link directly to the repository that contains the kernel for that specific device. If you are only linking to another thread or to a general repository, this will not be considered as being GPL compliant unless the code has not been modified.
3. If you are forking a repository that is similar to the examples listed above in #2, you MUST publish and link your entire kernel source. This includes any and all changes that you have made. Two of the most common ways developers publish their source on XDA is either with Gerrit, or GitHub. While these two methods are recommend, they are not the only routes you can choose to accomplish this. All that is required is that the source can be viewed and downloaded by anyone who wishes to do so. When releasing an update, your repository must be updated the moment you release your kernel on XDA. If you can post your update to XDA, there should be no reason as to why you cannot release your source.
What if the manufacture for my device has not released their kernel source?
In a perfect world this would not happen but unfortunately this is not the case. Pulser-G2 recently wrote a portal article explaining a certain situation that has come across our desks.
With all of that being said I will leave you with this...
By posting your work on XDA-Developers, you are agreeing that it complies with relevant licensing conditions. As such, by posting a kernel or other work containing GPL code, you are confirming to us that you have made this source code available publicly under the GPL. Failure to follow this policy will result in the closure of your thread and the removal of the download links.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}

PrismaKernel [R1] [OneUI3.x] [GSI] [Stable-Enforcing]

{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Hi friends
Here's a pseudo stock kernel
"Why pseudo stock?"
R = simple at the moment a stock defconfig is used with minimal changes while the rest are in the kernel source
"Why is the kernel called Prisma?"
R = that is quite simple because initially this kernel is a fork of the prish kernel, and also in the form of a tribute to one of my favorite anime, I forgot to mention that the temporary logo is based on said anime
Compatibility:
OneUI 3.x and GSI using the android 11 vendor as a base
Downloads: https://drive.google.com/file/d/1sfrlQ9-Lt88dNUFpZ_27_fTTdJqYNIiO/view?usp=sharing
Changelog:
-Basically most of the changes in prish except for the changes at the defconfig level, for example the governors are not enabled and / or configured
-Technically I did a kind of upstream to tag 116, I say that it is a kind of upstream because in everything I was investigating the change was only applied to the tag, basically the kernel was not modified
Credits:
Basically the same as in Prish plus a few people who helped me a lot, among which are
@Yillié for supporting my spam in telegram
@manudinath for supporting my spam in telegram, and explaining in detail things that I did not know about this device
@neel0210 by commits and fixes in Prish
Testers:
Considering that I am somewhat new to these things and very little known, only one person helped me by testing the kernel, although I do not know if he has an account in this forum
In case of finding serious bugs you can send me a message on Telegram @licht_estarossx
I am also open to suggestions
Source: https://github.com/KatoTempest/PrismaKernel_9611

reserved
Changelog:
R4
-upstreamed to 124 tag
-a setting only for aosp is being used in this version, so it might not work correctly in stock rom
-A small fix to the script (in twrp it looked pretty weird, but it's fixed now)
-This kernel build was compiled with google tools instead of lineage tools, maybe it works better / worse

manudinath said:
Click to expand...
Click to collapse
Something happens?

Very Nice my friend

Nah,
LichtEstarossx said:
Something happens?
Click to expand...
Click to collapse
Nah, no at all.

very good kernel, miss support for magisk modules, it would be nice if they partnered with some module to further improve performance.

This will also work for latest stock firmware right?

Nice

Could I flash this over with Odin using download mode to unbrick a phone (A51 Sprint 4G only)?

I'm wondering what's the benefit of this kernel?