[GAPPS][DAILY] Open GApps for Android; All Android Versions & Devices

dwardo

Senior Member
Jan 15, 2011
446
270
93
France
Hello,

I'm running LineageOS 17.1 on my Nexus 6 and my OnePlus 6T with OpenGapps (nano variant).

After a recent upgrade of both LineageOS build (2021 02 17) and OpenGapps (2021 02 13) on my OnePlus 6T my Android Auto (6.1.610534) started not being happy ("no app compatible with USB device") when connecting to my car head unit (Rlink2)
Screenshot_20210217-203311_Galerie.png


My Nexus 6 with Lineageos build from 2021 02 06 and OpenGapps from 2021 02 06 was still working flawlessly with Android Auto (6.0.615343) and my car head unit...

So I did a few tests on Nexus 6 to figure what was the cause : the LineageOS upgrades or OpenGapps Upgrades

Open Gapps 202102 06OpenGapps 2021 02 17
LineageOS 17.1 build 2021 02 06OKProblem
LineageOS 17.1 build 2021 02 17OKProblem

This clearly suggested OpenGapps was the culprit and was confirmed by downgrading my OnePlus 6T to OpenGapps build 2021 02 06 which also solved its Android Auto issue.

So something is not OK in OpenGapps builds 2021 02 13 to 2021 02 17... and maybe ealier as I haven't tested builds 2021 02 07 to 2021 02 12...
Anything <= 2021 02 06 works.

I can do tests if it can help narrow things down...


UPDATE:
Issue still present in openGapps nano 2021 03 05
 
Last edited:

kmdaksh

Member
Jan 28, 2021
25
5
3
Tested many times & found that Android System webview causing problems/crash during setup in Opengapps 11.0 arm64 30/01/20, if excluded setup goes through.
 

Cavaler

Member
Dec 26, 2012
35
5
28
Saint-Petersburg
Hello.
I am trying to use latest test version of GApps for Android 11 (HavocOS 4.2 ROM for Xiaomi Mi 9), and I encountered a problem.

Data migration from cloud is not working, since seemingly now Backup and Restore tool requires Data Transfer Tool (pixelmigrate), which is not installed:
03-05 14:51:57.808 8095 8095 E AndroidRuntime: FATAL EXCEPTION: main
03-05 14:51:57.808 8095 8095 E AndroidRuntime: Process: com.google.android.apps.restore, PID: 8095
03-05 14:51:57.808 8095 8095 E AndroidRuntime: android.content.ActivityNotFoundException: No Activity found to handle Intent { act=com.google.android.apps.pixelmigrate.ACTION_D2D_MIGRATE_FLOW (has extras) }
I managed to circumvent it by manually extracting AndroidMigratePrebuilt.apk from GApps package, installing it, granting it all possible permissions from GUI and also granting android.permission.WRITE_SECURE_SETTINGS manually via adb.

But I really hope it will be fixed in future releases.