New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
ADD Android 12L and Android 13 Versions #972
Comments
12L is covered by 6362c69, but 13 will need to be added. As for builds, the build server remains broken/down, so only unofficial builds can be generated at the moment. @nezorflame and @mfonville are working on a plan to restore the automated builds, hopefully not too long to wait. |
@osm0sis Have you managed to restore the automated build server? I'd really like to try an officially released OpenGApps 12L on a Samsung Tab T585 running LineageOS 19.1. Thank you for your work! PS: Is there anything I can help with? |
That's all @mfonville |
Thanks @osm0sis |
Hey! Even if the build servers remain offline, would it be possible for you to build android 12 and android 13 versions and add them on GitHub? Having these available would be amazing as I have quite a few devices that run either Android 12 or 13. Thanks! |
Judging from the lack of responses, I guess this project has been abandoned... |
Hi, yes, this is currently in low maintenance mode due to the lack of time
and maintainers.
As for the builds - I might do a few custom ones, but they will not be
hosted on GitHub, our only place for hosting is Sourceforge.
…_____________________________
Best regards,
Ilya Danilkin
On Tue, Mar 14, 2023, 11:11 Lorand Horvath ***@***.***> wrote:
Judging from the lack of responses, I guess this project has been
abandoned...
—
Reply to this email directly, view it on GitHub
<#972 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AA5ZZTVUDZQ6URSNP2HSSNTW4AKZRANCNFSM6AAAAAAR6MPW7E>
.
You are receiving this because you were mentioned.Message ID:
***@***.***>
|
Thank you @nezorflame We haven't abandoned the project, but we are in serious lack of time while meanwhile facing some major issues to resolve with bringing it back up to the quality we'd like to achieve @nezorflame can make some custom builds, I am in the process of setting up an alternative buildbot on another server (slowlhy progressing) and then we still have to review and do testing of the newer android versions. |
@mfonville @nezorflame Thanks for keeping us in the loop, very much appreciated! I would personally like to try an updated arm64 pico build for android 12L - something similar to what @ipdev99 did here https://forum.xda-developers.com/t/gapps-daily-open-gapps-for-android-all-android-versions-devices.3098071/post-86595145 @mfonville I'm rooting for you to be able to set up that buildbot asap! patiently waiting... |
Thank's for the update! If you decide to do some custom builds I will happily test them out. I have been missing this project! Best of luck to all of you with getting everything up and running again :) |
@mfonville Have you had some progress with the build server? |
Hi, yes, I got most of the stuff now set-up at the our Hetzner server, and should only do some minor fishing on it. The most major thing that currently needs fixing is to bring up our code-base and packages for the latest Android versions. Only then it would make sense for the buildbot to start building packages again. |
I'll be home in 2 weeks and assist with the updates.
…_____________________________
Best regards,
Ilya Danilkin
On Fri, Jun 9, 2023, 12:29 Maarten Fonville ***@***.***> wrote:
Hi, yes, I got most of the stuff now set-up at the our Hetzner server, and
should only do some minor fishing on it.
The most major thing that currently needs fixing is to bring up our
code-base and packages for the latest Android versions. Only then it would
make sense for the buildbot to start building packages again.
—
Reply to this email directly, view it on GitHub
<#972 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AA5ZZTRI47PP5MT2LIQVHFTXKMCIDANCNFSM6AAAAAAR6MPW7E>
.
You are receiving this because you were mentioned.Message ID:
***@***.***>
|
@mfonville @nezorflame That's great news, thanks for the heads up! |
Any updates on restoring the server? |
There's been this commit 5d723b0 and nothing since. This is not very encouraging. What's going on? |
@lorand-horvath Have you tried the MindTheGapps project which is recommended by the LineageOs wiki? |
I'm sure he is aware, and that's not what he asked or why. |
@AlexByte MindTheGapps has some issues on my device, so I went with @ipdev99 unofficial OpenGapps build from yesteryear https://drive.google.com/drive/folders/1ae_5jUOVG-spr63T0jyBpj6n3Anh4xKL Also heard good things about NikGapps. Again, for my device T585. YMMV. |
@lorand-horvath What issues? |
Guys, take this elsewhere please |
I'm going to ask @mfonville to lock this issue at least until this is implemented to prevent further off-topic. |
@nezorflame With all due respect, I think nobody here was even thinking about ads, nor encouraging use of other Gapps packages, on the contrary! We would all like to see and actually be able to use OpenGapps on Android 12+, but promises seem to still remain only that, promises. It's almost been a year since this issue was opened, why aren't we allowed to even discuss the situation? You could allow that much, otherwise what else can we do? If you have issues with the build server and manpower or something else, I offered several times to help, see above. Nobody took that into consideration. So again, can I help with anything to move development further? |
Like I said, no problem with you prodding the developers for more info and an updated timeline, it's just the off topic recommendations/discussion of other packages that shouldn't be done here. |
RIP? |
Hi there! I wanted to compile OpenGApps for Android 13, and when I hit an error message saying this API level wasn't supported, I searched around and found this issue. Does anyone know what has to be done to support Android 13? I may be able to help... |
Many projects have android 12L and android 13
The text was updated successfully, but these errors were encountered: