yashsingh1/xdaforums huggingface dataset:
[Android Software Development] :
I need a help, New Opengapps 9.0 Aroma packages causing me bootloops, Phone isn't booting up going back again to the TWRP
[Android Software Development] Crescendo Xenomorph:
confirmed on Lineage OS 16.0 - Xiaomi Mi 5s Plus

OpenGapps (Aroma 9.0 ARM64) - 20191107 build
[Android Software Development] :
On the latest AROMA builds if you uncheck all the apps & only let core app get installed, phone boots up.

I flashed 5 recent open gapps aroma builds all are ending up back to TWRP & you need to clean the system to flash ROM again otherwise it won't bootup.

Bro, I'd an older build from July which i had in my system luckily which i flashed at last to get my phone work again.

Something is seriously wrong with newer open gapps aroma builds published since 29th October

---------- Post added at 08:16 PM ---------- Previous post was at 07:55 PM ----------

Bro, can you fix the newer Aroma builds which are causing bootloops since 29the October till Today.
[Android Software Development] Nezorflame:
Did you install git-lfs? We're recently transferred to a fresh repos with LFS enabled.

Make sure you install lfs and try downloading again: https://git-lfs.github.com/

---------- Post added at 06:08 PM ---------- Previous post was at 05:48 PM ----------

I'll try to debug this, seems like some rogue APK update which will probably affect other versions as well.

In the meantime it'd be nice if you could provide me debug logs of the installation and the logcat of bootloop.
[Android Software Development] LilBlinx:
here you go
[Android Software Development] VincentJoshuaET:
Android 10 GApps should be installed on $SYSTEM/product/app or $SYSTEM/product/priv-app. Other files like libs and frameworks should also be in the product folder.
[Android Software Development] ipdev:
Thank you.

Apparently I was missing a step. (Step #2 in the link.)

I did not realize I had to initialize LFS by running git lfs install also.

One quick question about git-lfs.

The one in the link shows v2.9.0

The one I get by using apt install is v2.3.4-1

Should I change to the one in your link to avoid problems down the road?

Thank you.

Cheers.
[Android Software Development] :
New builds are flashing without problem. Thank you whoever fixed it.

But I'll be taking full back-up before flashing new build of Open gapps, in case things go wrong.
[Android Software Development] Nezorflame:
I think you'll be OK but I'd personally switch to the latest version provided by the authors: https://github.com/git-lfs/git-lfs/wiki/Installation#debian-and-ubuntu
[Android Software Development] armars:
Hello

why you dont update youtube version in aroma very long time?

it is stick with 14.34.54 very long time

please update youtube too

---------- Post added at 01:43 PM ---------- Previous post was at 01:43 PM ----------

Hello

why you dont update youtube version in aroma very long time?

it is stick with 14.34.54 very long time

please update youtube too
[Android Software Development] The_Walking_Playground:
Hi,

I just installed the latest 10 Beta GApps, released on 11/14. Finally I'm able to flash my ROM and GApps in the same recovery session and successfully boot the device. However, when choosing to restore from the cloud on a clean flash, I'm getting stuck in a perpetual "Checking info" loop and "Google Play Services keeps stopping". Is anyone else seeing this behavior?

TWP

EDIT: It seems even if I choose to skip the Restore step, I'm getting Play Services crash and I can't continue booting.
[Android Software Development] drewski_1:
I'm seeing similar with the "Checking info" loop, but I can skip and enter OS fine.

But i can't add my Google account (same "Checking info" thing) and the GApps I've tried crash out (Gmail, Chrome)
[Android Software Development] Crescendo Xenomorph:
OpenGapps Super / 2019-11-21 / ARM64 / Pie 9.0 no boot, RescueParty no matter what...

Lineage OS 16.0 - Mi 5s Plus
[Android Software Development] curiousrom:
Open GApps Fail to Boot?

Several users on different devices reported fail to boot if you select install the TWRP app when asked in TWRP. That app is fluff, wants to start at boot, run in the background, collect data & is not necessary anyway because the TWRP updates are not frequent & it's easy enough to update manually.

What happens if you install a smaller Open GApps package?

See Open GApps Package Comparison

***
[Android Software Development] Crescendo Xenomorph:
I never installed TWRP app...

The other I tried is Aroma, mine's ver 2019-11-13 / arm64 / configs in the attachment. Which is working OK.

Ah the configs used (removed & excluded apps - in respective format like in the Advanced Wiki) for Super is the same as the Aroma I use.
[Android Software Development] mkdante381:
Look on YouTube version in versionlog. This version is for Android 4.4+ with few permissions. Properly YouTube apk is sdk Android 5.0+. OpenGapps not repair this... Install OpenGapps without YouTube and download from play store latest version.
[Android Software Development] KKJdrunkenmonkey:
Bug in installer.sh

In the version I have downloaded at the moment (open_gapps-x86_64-9.0-stock-20191121) on line 1145 it says "nopdi" instead of "nodpi". Not a huge deal, looks like you'd end up rolling with nodpi instead of a higher density if you were affected by this bug, but thought I'd report it.
[Android Software Development] LilBlinx:
There is an issue with the latest Gapps when Google Conectivity services are installed. The READ_PRIVILEGED_PHONE_STATE permission is missing which leads to a bootloop.

--------- beginning of crash
12-01 08:37:51.665 1182 1182 E AndroidRuntime: *** FATAL EXCEPTION IN SYSTEM PROCESS: main
12-01 08:37:51.665 1182 1182 E AndroidRuntime: java.lang.IllegalStateException: Signature|privileged permissions not in privapp-permissions whitelist: {com.google.android.apps.gcs: android.permission.READ_PRIVILEGED_PHONE_STATE}
12-01 08:37:52.836 1710 1710 I wificond: wificond is starting up...
[Android Software Development] arm32168:
How to install Gapp on Device Rooted Without TWRP

Hi how to install gapp on devices is Rooted device can access /system and /data

possible to copy past file to /system and grant permission

tell me pls

Thank you very much
[Android Software Development] ipdev:
Hi again.

Need some help trying to figure out a mounting issue.

I get error 20 using 10-BETA on two devices.

The initial mounting of system seems to fail on these devices.

Both are being brought up to Android 10 (2SI-SAR)

Nexus 7 (2013) does not have the /dev/block/bootdevice/ path in TWRP.

Device currently has no official TWRP maintainer.

Pixel C has the /dev/block/bootdevice/ path in TWRP but, the partition names are not standard.

boot is by-name/KERN-A system is by-name/APP ... the TWRP maintainer will change the names if need be.

When flashed together the gapps installer errors out an is unable to unmount system (apparently it gets mounted?) so, you can just reflash opengapps_10 and it works because system is still mounted.

If you install the rom and then install gapps, system is not mounted after error gapps errors out.

Work-around.

Simply mounting system in TWRP, in-between installing the rom and opengapps_10_BETA

- Install ROM

- Mount system

- Install opengapps_10

On both devices, adding system symlink to /dev/block/bootdevice/by-name/ will then let you install both the rom and opengapps_10_BETA together.

If I add sbin/mount system in-between the Mount partitions and Detect A/B partition layout and system-as-root in the installer script, it works.

Or get more elaborate, and try something like this, which also works.

GitHub Commit - Link

Needs to be cleaned up. Please don't laugh too much at my coding skills. :D

Time to pull some new log files.

Nexus 7 (2013 WiFi - flo) Lineage17 and arm-10.0-nano-20191114-BETA

Pixel C (dragon) Lineage17 and arm64-10.0-nano-20191114-BETA

Debug Logs GoogleDrive - Link

Two sets for each.

- flo/dragon

- - rom and gapps.

- flo-bootdevice/dragon-bootdevice

- - Added /dev/block/bootdevice/by-name/system symlink (adb shell) prior to installing so I could flash together.

All testing is done with the newest device available TWRP and a complete clean flash.

boot, cache, recovery, system, and userdata (vendor also if an actually partition.) are erased/formatted with fastboot and only TWRP gets flashed to recovery.

For testing purposes, Wipe-> Format and Wipe-> Advanced (all partitions) in TWRP then reboot into TWRP. (An extra reboot after coping files to sdcard/ to clean up the logs.)

PS.

SetupWizard does not work on Nexus 7 and removing provision partially breaks the UI.

Then again.

- It is arm and I'm not sure if an arm SDK29 SetupWizard exists yet.

- Lineage 17 is still being brought up.

Sorry for the long post.

Cheers all. :cowboy:
[Android Software Development] followmsi:
[MENTION=7280276]ipdev[/MENTION] - Thanks for driving this !

But as mentioned before .. the problem is different.

We don not need to change partition names .. etc.

I fixed it now .. "Mount /system partition too"

https://github.com/followmsi/opengapps/commit/e8e960e838371259181baadf31d14cbc90e80d37

Pls check with opengapps team and pls take care to get this minor change merged into opengapps sources.

Just repacked a test package quickly .. open_gapps-arm-10.0-pico-20191114-BETA-test.zip

This way we can install rom, opengapps and magisk in just one TWRP queue. :)

Cheers

EDIT:

Let me quickly add my comments ..

Maybe it's better to change this line .. https://github.com/followmsi/openga...37#diff-4b4d756dd3b2a232970b47588e486eddL1058

grep -q "/system.*ro[\s,]" /proc/mounts && mount -o remount,rw $SYSTEM_MOUNT || mount -o rw "$block" $SYSTEM_MOUNT

Because I have added "/system" to "mounts" the remount will work.

mount -o remount,rw $SYSTEM_MOUNT

After the "II" (OR) the script wants to mount .. "$block"

mount -o rw "$block" $SYSTEM_MOUNT

Like you did - If you add symlink for "block=/dev/block/bootdevice/by-name/system" you make the "mount" command working.

As we dont have slots "$block" will be defined here https://github.com/followmsi/openga...37#diff-4b4d756dd3b2a232970b47588e486eddL1038

block=/dev/block/bootdevice/by-name/system

Just for better understanding ..
[Android Software Development] ynamojn:
I am using LOS16 on Leeco Le Pro3 (ZL1). Dirty flashed 4 December nano version build caused bootloop. I thought it was because of the permissions of Google Connectivity Services. Apparently it was not since editing the permission file didn't affect.

Anybody experience the same thing?
[Android Software Development] :
Yep, for me the same. OnePlus 3 LOS16, 4th Dec nano package
[Android Software Development] curiousrom:
Re: Open GApps Nano 2019-12-04 Bootloop?

Failed to boot & thrown back to TWRP: clean install w/ Format Data + wipe System LineageOS 16.0 on Samsung A5 2017, most recent official twrp-3.3.1-1-a5y17lte.img.tar and open_gapps-arm64-9.0-nano-20191204.zip. Long thread here on Reddit.com/r/LineageOS before we found the problem.

The solution was to Format Data + wipe System again & install LineageOS 16.0 + Pico 2019-12-04.

Could you guys attach the Open GApps log please? :cool:

***
[Android Software Development] jdrch:
Same issue with the 20191204 build booting back to recovery after being flashed with latest LOS 16.1 Nightly. Fixed by restoring the previous good Nandroid backup and then dirty flashing the same LOS Nightly build.
[Android Software Development] LilBlinx:
It is fixed Update privapp permissions

This time it was the WellBeing permissions

12-05 07:27:19.053 1223 1223 E AndroidRuntime: java.lang.IllegalStateException: Signature|privileged permissions not in privapp-permissions whitelist: {com.google.android.apps.wellbeing: android.permission.LOCATION_HARDWARE}

Previously it was the Google Connectivity Services

12-01 08:37:51.665 1182 1182 E AndroidRuntime: java.lang.IllegalStateException: Signature|privileged permissions not in privapp-permissions whitelist: {com.google.android.apps.gcs: android.permission.READ_PRIVILEGED_PHONE_STATE}
[Android Software Development] curiousrom:
Re: Open GApps Nano 2019-12-04 Bootloop?

Then ALL builds 2019-12-04 must be deleted ASAP.

[MENTION=2010892]Nezorflame[/MENTION] & [MENTION=1763928]MNBooZe[/MENTION] (NicholasBuse on GitHub) - I see almost 3,000 downloads here https://sourceforge.net/projects/opengapps/files/arm/ and an other 3,000 here https://sourceforge.net/projects/opengapps/files/arm64/

That's a lot of users wasting their time with broken builds.

This happened a couple of times recently. The general public is not a beta tester group.

Maybe it's time to create one?

Edit: Why not switch to a weekly build instead of daily & test properly before launch?

***
[Android Software Development] LilBlinx:
I agree on this one!

1. The Gapps packages which are pushed to the OpenGapps project have (beta) tags. Most of the times, Google Maps couldn't be updated because of that tag.

2. The OpenGapps packages aren't tested before release.

3. Most importantly, the access to the GitLab project is closed and anyone that requests access to it is either waiting indefinitely for one simple pull request.

I am building ROMs on daily basis and flash or build OpenGapps, so it is easy for me to detect and fix the issues by myself, but the general public isn't. What I suggest is to delay the builds by one day so the "testing" group or whatever you want to call it can detect the issues.

I left comments on the commits with the permissions that are in need of fixing and the correct permissions for them but apparently the communication is internal i.e. the communication is only between the people that are members in the organization and ignore any other user.
[Android Software Development] Nezorflame:
First of all, thank you for your feedback.

The issue with the apps was that they required new permissions which was resolved by this PR: https://gitlab.opengapps.org/opengapps/all/merge_requests/3

Next build should be fine, we'll remove the faulty ones.

EDIT: removed, website now shows packages from 27.11 as the freshest ones.

While I agree that the builds could be done in a weekly basis with a more thorough testing process, right now it's an automated one. APKs are being updated automatically, builds are done by a build server automatically and pushed to the SourceForge. That's just the way it works.

Since we have to rely on Google for not breaking the compatibility (and they happily ignore that), this current process is flawed and bugs like that are happening (and most probably will happen again).

Now, if the aforementioned testing could be done automatically as well, we'd be happy to do that. But since it's almost impossible (at least, with the current infrastructure), we have to rely on your feedback (and our own when we're flashing new builds). If you're willing to become a tester, or have suggestions how that testing can be done, we'd be happy to hear your take on this.

Until then, I'm afraid we don't have much options.

As for the weekly builds, I actually like the idea and will discuss this with the team. Or maybe [MENTION=1763928]MNBooZe[/MENTION] and [MENTION=359586]nicholasb[/MENTION]use would share their thoughts here.

---------- Post added at 08:36 PM ---------- Previous post was at 08:32 PM ----------

1. Yes, some of the APKs come in the beta state as well, I'll ask Nicholas if we should maybe separate them/make optional or exclude from the builds.

2. Yeah, see my previous post. I like the idea of a testing group if there are people willing to do that (I kinda already do that in the unofficial group in Telegram with Q builds, so maybe it's time to make it official or create a new one here/on other medium).

3. I've already enabled forks few months ago, so if you're still unable to create one, please contact me and we'll resolve this.
[Android Software Development] LilBlinx:
Thank you for your response.

I haven't worked much with GitLab because since I know about myself I am on GitHub. Apparently there was an issue with the SSH keys on GitLab from my side, I've generated new ones and now I can fork the project.

I like the idea of making a test group or extending it to official. As I said, I am building these packages by myself so now that I have access to forking the repos, I can help in resolving few issues here and there.
[Android Software Development] bflmpsvz:
Hi, is the project dead? I must update GApps from package (Google Play updates Play Services not properly).
[Android Software Development] amirizad_7436:
This project will be death when Google die..Lol

What's the exact problem bro?
[Android Software Development] bflmpsvz:
Why's the exact problem? That the binaries weren't updated since 27th November, that's it (i don't believe this project is launched by Google)

________________________
[Android Software Development] sanguinesaintly:
If the last stable version is 27th November then just live with that. Your phone won't stop working and the world won't end. I'm not being facetious, just realistic. It doesn't really matter.
[Android Software Development] amirizad_7436:
Yep it's not by Google

Like many pixel experience custom roms that are available for many phones and make our phone like Google pixel

Btw:devs can't update packages with each update that Google release.they just update packages for important things.and we can easily update them from play store

GL
[Android Software Development] Nezorflame:
We had a 12/04 release which was broken. We pulled it from the website, buildbot has undergone some maintenance and the next build should be fine.
[Android Software Development] Finchy11:
Is there any chance for Andoid Q gapps update in nearest future?
[Android Software Development] curiousrom:
Are We There Yet?

50/50.

Edit: [MENTION=4997341]Finchy11[/MENTION] check the progress in this page & the dev's posts about asking for ETA: Pull request - Android 10 #773

***
[Android Software Development] Black_Stark:
Why most google apps have dark theme but aosp apps dont change to dark theme in android 10?
[Android Software Development] curiousrom:
AOSP Apps Dark Theme?

Because Google has an army of very well paid engineers while for the AOSP apps it's a work in progress:

site:android.googlesource.com/platform/packages/apps/ dark theme

https://android.googlesource.com/platform/packages/apps/

https://developer.android.com/guide/topics/ui/look-and-feel/darktheme

XDA article: Android Q’s Dark Mode: How Google’s next Android OS will tackle blindingly light themes
[Android Software Development] Nezorflame:
Regarding the posts https://xdaforums.com/showpost.php?p=81087555&postcount=6367 and https://xdaforums.com/showpost.php?p=81099773&postcount=6368

[MENTION=7280276]ipdev[/MENTION] [MENTION=5480152]followmsi[/MENTION] that was a good investigation guys, thank you both.

Wanna throw a PR inside of my branch to get it merged? Or should I just integrate your changes into the build with the mentions?
[Android Software Development] Nezorflame:
OK guys, it's time for the new Q beta builds.

What has changed:

- ARM finally launches fine: tested with my old trusty N5 and got another report that it works

- added latest permission fixes for the GCS and Wellbeing (LOS still doesn't have an overlay for the Wellbeing, will try to make one myself in the next release)

- Pixel Launcher works now, thanks to the overlay from [MENTION=7170589]Love4Taylor[/MENTION]: https://xdaforums.com/showpost.php?p=78029447&postcount=483

- more /product fixes, should cover up the last cases

Links:

- ARM: https://sourceforge.net/projects/opengapps/files/arm/beta/20191209/

- ARM64: https://sourceforge.net/projects/opengapps/files/arm64/beta/20191209/

As usual, this needs more tests from you people, so will wait for the feedback.

Right now it seems that we're very close to release. I'll make sure to fix the remaining issues as soon as possible (assuming I still have my daily duties eating most of my free time), so stay tuned for more updates in the upcoming days.

EDIT: while testing ARM package, found out that setting up the lockscreen makes the device go into the bootloop.

If the same happens to you, reboot to recovery and delete the /data/system/lockscreen files to be able to boot. I'll fix that ASAP.
[Android Software Development] ipdev:
I missed that system was actually not being mounted.

Thankfully [MENTION=5480152]followmsi[/MENTION] noticed it.

Adding /system back into the mount list seems to work.

I tested it on a few devices with Android 10, arm/arm64/arm64-slot.

(Nexus 7, Poco F1, Pixel C and Essential PH-1)

I wanted to make sure that it didn't seem to break anything.

Finished testing on Android 10 as much as I could last night.

(I do not have a true A-Only SAR device to test on.)

Sent a PR to your github ten-cleanup.

(I only wanted push the the last commit but it grabbed all three.)

I am still a little confused by the mounting part of the BETA/ten installer script(s).

I have some questions and ideas to figure out yet but, for now adding system back to

mounts seems to be the easiest option.

Mounting system separately a better course ?

(Not sure.. )

I haven't tried (or fixed) this yet but, it's what I plan to try/test next.

GitHub Commit - Link

Needs to be fixed/cleaned up. (Ignore mk_test_arm.sh and sources, apparently I forgot to update my gitignore.)

I use double # to comment out original lines for testing. (Easier to find my changes.)

Please don't laugh too much at my coding skills. :D

Cheers. :cowboy:
[Android Software Development] MajorBoobage:
I have trying to find information how to remove gapps that are included in the ROM (EvolutionOS 3.4, for Mi 9T Pro/K20 Pro) and install Opengapps nano/pico instead.

Can anyone help?

Many thanks!
[Android Software Development] mcfouch:
You can find an exemple made some years ago on OneplusX phone :

https://github.com/opengapps/opengapps/wiki/gapps‐config-for-OnePlus-X's-OxygenOS

All options are describe on Opengapps wiki, Advanced features and options :

https://github.com/opengapps/opengapps/wiki/Advanced-Features-and-Options

Good luck!
[Android Software Development] MajorBoobage:
Awesome! Thanks!

You think this will work on Q?
[Android Software Development] curiousrom:
Decrapify Custom ROM?

Why don't you ask the question to the dev of that ROM as only him knows what exactly he included in it? :confused:

Or in the thread where you found it?

***
[Android Software Development] MajorBoobage:
I tried that too, posted already three times in Evolution thread, and three times on telegram group, no replies so far on either.

Asked in this thread, got at least some useful info in less than a couple of hours.

Devs seem to be too busy to answer questions, which I guess is understandable.
[Android Software Development] MajorBoobage:
The code is here:

https://github.com/Evolution-X?page=1

If anyone feels like helping me finding the right location/name of the gapps in order to modify the opengapps config file.
[Android Software Development] cheanch:
Hi,

I was trying to flash the Gapps for Android 10 from the 12/09 builds, but I'm still getting the error below -

I built my AOSP directly from the Google branch(QP1A.190711.020) for Pixel 2, and I can verify the OS version is 10 and SDK 29 from the system Setting. Any advice is appreciated. Thanks.
[Android Software Development] curiousrom:
Re: Open GApps Android 10 Beta 2019-12-09

You can contribute with a report, attach the Open GApps installation log & logcat if relevant in GitHub/Open GApps & follow the development of this project here: Pull request - Android 10 #773.

***
[Android Software Development] yoshkapundrick:
I erased the locksettings files. Mine did not have the gatekeeper files. Still no luck. It seems the locksettings files regenerate after a failed reboot..
[Android Software Development] JohnMalc:
Hi, I am using this rom and your beta release and unfortunately after phone bootsup into the rom, i can not setup any google play service related apps (like gmail, etc. but not firefox or youtube for example) because it keeps crashing. i have tried already updating the google play manually but so far nothing helps

EDIT: already fixed, sorry