yashsingh1/xdaforums huggingface dataset:
[Android Software Development] rahulbarai:
I have installed Aroma lp gapps 07-25 on CM 07-25 build, without any issue. Its working fine and everything is up-to-date.
[Android Software Development] manpildo:
Hi,

Anybody else experiencing this problem in Maps? This happens when going to "Your timeline".
[Android Software Development] hanschke:
micro build dont install latest play service here. apkmirror is newer ;)
[Android Software Development] MastahF:
Today's timing of having and uploading the new play services, and the moment the snapshot is taken for the daily builds, were unlucky. Tomorrow the new play services will be in all the builds.
[Android Software Development] raptir:
Kind of an aside here, but does anyone else have a lot of trouble when they flash a Gapps package that needs a play services update? It took me several reboots and clearing the Play Store data to get my apps to show up after Play Services updated on its own. If I flash back to stock and let play services update it doesn't give me nearly as much trouble.
[Android Software Development] djalfy:
I don't know if this is happening only to me, but I've noticed that every package has a problem with the initial setup of the phone at the part where I must enter the two-steps verification code after entering my google account credentials. At that step I get an FC and I have to enter my credentials 2 or 3 times to succeed.
[Android Software Development] abacate123:
Hey [MENTION=6404745]MastahF[/MENTION] I just saw the new website design it's amazing bro pretty awesome work! Luv yu.
[Android Software Development] validatus:
Hi boys

Impossible to access OPEN GAPPS PROJECT

sorry now at 19:50 it's ok

GALAXY TAB PRO 10.1

cm-12.1-20150729-NIGHTLY-picassowifi

open_gapps-arm-5.1-stock-20150728

excellent but clock stops after booting

regards
[Android Software Development] MastahF:
Most of the work was done by [MENTION=4964524]raulx222[/MENTION] by using the GetMDL toolkit.

I just fiddled with the javascript to get all the scripting working and to work around the MDL quirks.

PS: If anyone would be interested in material design websites, I am sure [MENTION=4964524]raulx222[/MENTION] could use some extra source of income when he will be starting his study ;).
[Android Software Development] abacate123:
Ok, nice, I really do like the new opengapps logo. Look cool. Will you add the logo on the OP?
[Android Software Development] MastahF:
I will add it, thank you for suggesting it. The logo is btw designed by [MENTION=5185457]Yeti12[/MENTION], he has a website with the material design logos he develops at http://www.yeti-designs.com/
[Android Software Development] raptir:
The new site looks great but is there a way to open the MD5 directly in the browser like before? Makes it a little easier to check it.
[Android Software Development] Ok_Kaleidoscope5109:
I never saw the update til now. Anyhow, I tried yesterday on my TouchPad for 4.4 Micro Gapps and it worked perfectly. Thank you for helping me bring my 4 year old tablet back to life. It's a POS.
[Android Software Development] MastahF:
The format that it is now presented in, is compatible with all recoveries, so your recovery will check automatically if the md5 matches if you download it together with the package.
[Android Software Development] dnle71:
Gonna try this over tk-gapps and see if this saves more space.
[Android Software Development] MastahF:
It might be a bit smaller, because TK GApps does not use DPI-optimized variations of the apps, so the app optimized for your device might be a little bit smaller if it has e.g. lower-DPI resources. But that difference in size will be neglectable. But a very large improvement you'll find is *speed*. Because your device does not have to scale the application resources at runtime anymore, it will run faster and battery usage will be lower.
[Android Software Development] dnle71:
Really? That's more like it!

You see my main problem is tk-gapps is most apps of stock gapps is essential to me. But, my Nexus 7 2013 has limited space even if I use gapps-config and trim it until I get pass to at least install it.

I usually use stock gapps but I've seen a nexus version is it ok to use stock over nexus gapps?
[Android Software Development] MastahF:
You best stick to stock, if it does not fit on our /system/ partition anymore, I would recommend to use Aroma and deselect some of the packages.

The 'For Nexus' version is a special release that can be installed on Google's Rom, not on AOSP/Cyanogenmod. Look for details about that release at xdaforums.com/android/general/alpha-gapps-stock-t3093389
[Android Software Development] dnle71:
Thanks! But I'll stick to using gapps-config, I like it better!
[Android Software Development] raptir:
Are you using CM by any chance? I noticed that the system partition on the CM build for the Nexus 7 2012 is very small and will not fit a full gapps package, while the partition is larger on the stock ROM.
[Android Software Development] bovirus:
Please atke that there is a problem about pico apckage for Androdi 7.1 about size.

pico package 13.12 - 97 MB

pico package 14.12 - 133 MB

pico package 15.12 - 133 MB
[Android Software Development] nighthowl:
Thanks to everyone who worked for this project!
[Android Software Development] RufioHugo:
Update to arm-7.1-micro 17.12.2019 deletes, changes settings and disables functions

Updated this morning to … arm-7.1-micro 17.12.2019 on DualSIM with 7.1.2

Issue description:

After update following was deactivated;

- developer mode = and I can't reactivate it

- screenlock (wipe) = and I can't reactivate it

- home button = and I can't reactivate it

- menu button = and I can't reactivate it

- deleted all SIM-mapping = I was able to reaactivate it

- and so on

Reproduction Steps:

- Reinstalled a full backup on phone (arm-7.1-micro 14.12.2019 on DualSIM with 7.1.2)

- All works fine / as before

- Update to arm-7.1-micro 17.12.2019 on DualSIM with 7.1.2

- Many malfunctions, nonfunctioning items & a partly unusable phone

Expected behavior:

Update & work as before ...

Observed behavior:

As written down … I'm still testing and finding more and more problems

~ 1. Update of issue ~

- update deleted all users except the last active one & the left user has no rights, not even view his own data

- pull down menu on start screen doesn't work anymore

- notifications come only with sound, no popup / no icon

- the power button only shows "power off"&"restart", no longer the 4rd option

- back-button goes 1:1 back in history and seems to close app

- silently activated some (before deactivated) options in google play store and apps

At this time I'm not able to provide any log - adb won't connect filemanager acts weird!
[Android Software Development] FlamurKasa:
I just went from Oxygen OS 9.0.6 to this custom ROM running android 10 on my Oneplus 3T.

Followed the ROM install instruction using the Arm64 nano package provided in post #6389 (of this thread).

All seems to be working perfectly so far. Will post again with updates if anything misbehaves. Let me know if you want me to test a known issue.

Keep up the good work :)
[Android Software Development] ipdev:
[MENTION=2010892]Nezorflame[/MENTION]

Not sure where the best place to discuss the 10 beta build(s) is.

(Is GitHub or GitLab better?)

I'll make a quick note here since I'm still testing.

The latest 201912xx 10 beta builds partially break the ui or force close the default launcher on some of my devices.

(trebuchet, lawnchair, crDroid Home)

It seems the PixelDefaultsOverlay is the culprit.

I was running tests quickly for results and not grabbing logs tonight.

By removing PixelDefaultsOverlay from wellbeing in inc.buildtarget.sh, nano and below installed without issue.

When I tested micro and above, pixel launcher (with the overlay) worked fine but trebuchet and the others were broken.

I'll try to narrow it down a little more and then grab a full set of logs to post.

Just wanted to let you know.

Cheers.:cowboy:

PS.

Please let me know if there is a better place to post/discuss issues with the 10 beta(s).
[Android Software Development] Nezorflame:
Thanks for reaching out! Both XDA, GitHub/Gitlab or Telegram discussion group are fine, but I'm more active in the latter one.

As for the issue, I'm gonna need to research this more. The point of this overlay is to set Pixel Launcher as the default, so other launchers will crash unless they're set as the default as well e.g. with Quickswitch.

I've added fix for the Wellbeing into this overlay as well (and since this overlay sets the default launcher without actually installing one, this seems to be the origin of the issue), but it seems that I need to make a separate one instead, so I'll start with that and make a new test build (hopefully by tomorrow).
[Android Software Development] cmohan0004:
how did you fixed it? same problem with me, when i flash stock pack i cant pass setup because google play services keep stopping, it only works with nano pack.
[Android Software Development] :
If nano package works for you for passing setup then you're fine. After setting up your system with nano package then you can "upgrade" / flash easily stock package. Done. Should work smoothly as a workaround ;)
[Android Software Development] r6680jc:
Hi, which latest version of Google Photos app that's still standalone apk? Is it 4.13 (like you said in your previous comment) or 4.18 4.19 (latest available on apkmirror)?
[Android Software Development] notnola:
I'd like to join the discussion, yet can not find a link to the groups' Telegram anywhere! Mind sharing that link?
[Android Software Development] zwonko:
Having problem with apps on app store. Installaed lineageOS14.1 on Asus Zenfone ze500kl and open_gapps-arm64-7.1-nano-20191221. The problem is that Google Play Store not showing many apps (ie facebook messenger) and other are very old date (ie Youtube version form 2015). Someone have similar problem?
[Android Software Development] Wolfcity:
Maybe update TWRP. What device? What ROM?

As you try to install Gapps for 4.4 the device is an older one, is there enough space in /system partition?

Provide a recovery log or at least the gapps log.
[Android Software Development] amirizad_7436:
Did you try different versions?

And make sure that you have latest odin
[Android Software Development] amirizad_7436:
Sorry to ask again but i just wanna know that did you flashed various versions of twrp?(not just one version for many times!)
[Android Software Development] amirizad_7436:
So try another versions

For example 3.3.0 or even 3.2

Not much different

Btw: Don't forget to untick auto reboot at odin

When it passed on odin just turn of your phone and go to recovery directly

Edit:as i know for flashing android Q you need special twrp that doesn't work on other things and just can flash Q rightly!

Ask your dev for further information
[Android Software Development] curiousrom:
Off-Topic TWRP & Unofficial LineageOS 17 Question

Errr… sorry but this is not Facebook where anything goes. :eek:

The threads on XDA have specific topics and I don't see any Open GApps problem in your post which is the topic of this thread. ;)

And official LineageOS 17 does not exist yet.

If you need help with an unofficial custom rom then go to the thread where you got it from to get help as who knows what's in it exactly.

And there you might find actual users of that unofficial OS & the same device with similar questions.

Good luck!

***
[Android Software Development] guhvanoh:
And this has what to do with gapps??? Post in the Q & A section of your device.
[Android Software Development] 7wells:
Hello and a Happy New Year!

Is it still correct to leave the stock dialer as is if the Google dialer is selected so as to avoid problems with emergency calls? Should the dialer frameworks always also be selected together? Thanks for your help and everything.
[Android Software Development] Nezorflame:
Sure, come and join at https://t.me/opengapps_discussion
[Android Software Development] Saitdark:
I flashed Pixel Experience (no gapps at all). After that I tried flash Open Gapps. I use SD710 and pick arm64 ver, I got error said not compatibility (@@), I flashed arm32, It said the ROM has gapps stock (not) but install it succesfully anyway. But after boot nothing show up. (TWRP 3.2.3)

So what's wrong with something though?:eek:
[Android Software Development] Tech_Expert:
Hello! Why are all the Android 10 Gapls downloads grayed out? :)

---------- Post added at 10:30 AM ---------- Previous post was at 10:30 AM ----------

Hello! Why are all the Android 10 Gapps downloads grayed out? :)
[Android Software Development] Black_Stark:
Coz its not official yet. In beta stage.
[Android Software Development] RaffNix1982:
But how to download gapps for Android 10?

Gesendet von meinem ONEPLUS A3003 mit Tapatalk
[Android Software Development] mcfouch:
A very little search drive me here : https://sourceforge.net/projects/opengapps/files/

Android 10 current state

Right now SDK29 packages are in beta state.

You can find them in the corresponding folders:

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

ARM64:https://sourceforge.net/projects/opengapps/files/arm64/beta/
[Android Software Development] Nezorflame:
Aight, new builds coming right up!

What's changed:

- new mounting scripts have been implemented (thanks to [MENTION=4544860]osm0sis[/MENTION]) - this may still have issues, but right now looks promising and should fix all these "unsupported device" errors

- Actions Services is now shipping by default in micro+ variants to support Pixel Launcher

- new overlays for Pixel Launcher, Actions Services and Wellbeing to use them as the default packages to stop FC'ing

- synced versions of Chrome, Google Webview and TrichromeLibrary to make them work together without issues

What needs to be checked:

- installation process: you should be able to install it without any issues

- logging into account: should work, restore should work as well without FCs

- Digital Wellbeing: should work fine without FCs

- Pixel Launcher: should be settable as the default launcher and work without FCs with Suggested apps row

- Google Photos: should launch without FCs (for now looks still broken for me, but I want to hear more results)

Please provide full feedback on reporting issues with logcat.

Links:

ARM: REMOVED

ARM64: REMOVED

See the post below: https://xdaforums.com/showpost.php?p=81476175&postcount=6435
[Android Software Development] Nezorflame:
[MENTION=7280276]ipdev[/MENTION] if you have some time, please take a look at well.

---------- Post added at 02:59 AM ---------- Previous post was at 02:58 AM ----------

Try the new build and let me know if the issue is resolved.
[Android Software Development] Nezorflame:
There are issues with Google Webview and mounting script, so I'll delete this build mentioned above and publish a new build in a few with fixes.

---------- Post added at 02:36 AM ---------- Previous post was at 02:35 AM ----------

Aroma doesn't work on newer devices. Nothing will help.
[Android Software Development] ConnerJSP:
Is there any fix for the Pixel Launcher crashing due to navigation gestures? Wondering if its GApps or ROM contents (overlays and such) that causes this.
[Android Software Development] ipdev:
I saw the massive rewrites yesterday. (Now two days ago.)

No small task there. :)

Pulled the updates and made a pico and nano build to test when I got home tonight.

The new mounting script worked great.

Worked on arm, arm64, slot and non-slot devices.

A/B SAR as well as 2SI SAR devices.

- Not sure about A-Only SAR devices. (I do not have one to test on.)

The new overlays (using pico and nano) did not seem to break Quickstep or Trebuchet default lunchers.

arm and arm64 devices.

SetupWizard is still crashing (fc) on arm when skip WiFi. If you connect WiFi then it crashes when trying to skip Google account login.

I normally skip though the setup and only adjust time and date. Everything else is setup after. I just prefer to stay offline until I uncheck / toggle off a few google and other settings.

On arm64 devices, the SetupWizard works as it should, you can skip though it without a force close. The only oddity is screen lock. On one device it's more like pixel (just skip it) on another you have to select screen lock setup (pin/pin-password/pattern..) then select skip.

Time for bed but, I just wanted to let you know.

Note:

arm devices were also tested with a modified version to circumvent SetupWizard.

(Removed SetupWizard and OneTime installer.)

Devices quickly tested on:

Essential PH-1 [candy]

Pocophone F1 [gzr/validus]

Nexus 5 [lineage]

Nexus 7 (2013) [lineage/aex/cr]

Cheers. :cowboy:

PS.

Will grab logs next time.

Since arm64 devices seem to be working, most likely from Nexus 5 or 7.
[Android Software Development] danwood76:
SetupWizard crashing on ARM devices is caused by google moving the TimeZoneFinder class in libcore from libcore.util.TimeZoneFinder to libcore.timezone.TimeZoneFinder.

I have created a wrapper for this class in our common device tree, not sure if this is the best way to do it but it works:

https://review.lineageos.org/c/LineageOS/android_device_samsung_universal7580-common/+/267020

[MENTION=2010892]Nezorflame[/MENTION] is this something you could integrate in OpenGapps?

Regards,

Danny
[Android Software Development] Nezorflame:
This is the next focus point - without the Actions Services it crashed all the time, now at least it's working but the gesture part is a mystery for now.

---------- Post added at 11:58 AM ---------- Previous post was at 11:48 AM ----------

That's a great find! Not sure how it can be implemented though, I'll ask around (or if you know a way, feel free to reach out either here or in Github/Gitlab/Telegram).
[Android Software Development] danwood76:
I don't really know.

My Java wrapper produces a jar file which is added to the device framework so that it is then be added when dex2oat is run, the APK gets compiled/optimised with my wrapper and so it's loaded when SUW runs and works around the issue (tested with your latest open-gapps pico).

Unless there is some way of pre-loading an APK with a jar? I don't know that much about the APK side of Android.

Regards,

Danny
[Android Software Development] Saitdark:
TWRP 3.2.x was at fault. I change to another ver and it works.
[Android Software Development] Nezorflame:
Builds have been updated, feel free to take them for a spin:

ARM: REMOVED

ARM64: REMOVED

Edit: there were mounting issues this time, so I've pulled that release as well.

See this post for the new beta: https://xdaforums.com/showpost.php?p=81495411&postcount=6449
[Android Software Development] aR_ChRiS:
Tried on my OP3T with Nitrogen 10 (most recent build)

However it seems that the package could not read the buildprop file thus it could not be flashed...
[Android Software Development] Nezorflame:
Guys, for those who faced the mounting issues in the last build - please test these nano packages to see if it's resolved:

ARM: https://sourceforge.net/projects/op...apps-arm-10.0-nano-20200115-TEST.zip/download

ARM64: https://sourceforge.net/projects/op...ps-arm64-10.0-nano-20200115-TEST.zip/download

cc [MENTION=3373119]aR_ChRiS[/MENTION]
[Android Software Development] psshirke.shirke@gmail.com:
Device : Xiaomi mi 3

rom : Android 10 aosp by vasishath

twrp : Multirom twrp (recommend)

gapps : Arm latest 15/01 build

getting error 25
[Android Software Development] Nezorflame:
New test builds:

ARM: https://sourceforge.net/projects/op...ps-arm-10.0-nano-20200116-TEST_2.zip/download

ARM64: https://sourceforge.net/projects/op...-arm64-10.0-nano-20200116-TEST_2.zip/download
[Android Software Development] Wishmasterflo:
Thanks. This one is working fine.

At least for me:

Oneplus 6

AOSiP 10

TWRP 3.3.1.16
[Android Software Development] Nezorflame:
Builds have been updated again, this time initial tests showed that mounting finally works :)

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

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

Known issues left:

- Photos still FC, I have a possible solution for that but will be testing it further in the next build

- Trying to use Pixel Launcher with Q gesture system will result in FC, for now avoid using them together

- [ARM-only] SetupWizard seems to be crashing for some due to Google changing some stuff (more details here - https://xdaforums.com/sho...ostcount=6439)

Test them out and let me know!
[Android Software Development] curiousrom:
Open GApps Android 10 Beta

You forgot to delete the 20200115 folder with the defective build: https://sourceforge.net/projects/opengapps/files/arm/beta/20200115/ Done, thanks. :good:

Instead of linking directly to the download folder for a given build date and having to edit your post if they are removed like you did above why not just write for example:

Get the most recent Open GApps Android 10 Beta builds here:

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

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

***

Why not attach the TWRP log and/or the open_gapps_log.txt created in the folder where the Open GApps was when you flashed it except if you used sideload on your computer @ the present?

***
[Android Software Development] ipdev:
Thank you. :)

I asked followmsi to take a look and he added it to flo/deb (Nexus 7 2013 WiFi/LTE).

He had the same question ..is it possible to integrate this stuff into Gapps instead of device tree ?

I am happy to confirm your wrapper works on the 2013 Nexus 7 with unofficial lineage 17.1.

Nexus 7 (2013) unofficial lineage 17.1 now includes [MENTION=6707196]danwood76[/MENTION] wrapper (arm patch).

I used the nano and stock packages for testing.

open_gapps-arm-10.0-nano-20200116-BETA

Android SetupWizard - Skipped most, set time and date, toggled off most of the google crap.

open_gapps-arm-10.0-stock-20200116-BETA

Using a gapps-config file, Setup WiFi, Google account, time/date was automatically corrected since WiFi was connected. Took a little long at checking for updates but, all worked.

Notes:

I install via adb sideload.

Pushed gapps-config.txt to /sdcard/Open-GApps/.gapps-config when using stock.

Attached my gapps-config file for reference.

(Use the Include option and the file is a little outdated but, the tag options still seem valid.)

Cheers all. :cowboy:
[Android Software Development] curiousrom:
Re: Open GApps Android 10 Beta - Build 2020-01-16 Report

Thanks for the report. :good::cool:

Official LineageOS 17.1 is not launched yet so to avoid creating confusion for users it's important to mention that it's for an unofficial version & only for that device. Including a link to it's thread would be a good thing IMO.

Could you confirm what you wrote in your interesting Pull request - Copy logs to sdcard/ when using sideload #794:

If so, could you edit your post above & attach the open_gapps_log.txt to it please?

***
[Android Software Development] Nezorflame:
Thanks, indeed, removed it.

Because I like it this way.
[Android Software Development] bersem:
[MENTION=2010892]Nezorflame[/MENTION] can u take a look into a log from TWRP and another file please. A big major issue on SM-G900F S5 with opengapps. Afer fresh clean install LOS 17 ROM + opengapps successfully boot into sytem. Initial-Setup works fine.

After reboot or shutdown it doesnt boot anymore. Only stucks on bootlogo...

2nd file: https://xdaforums.com/showpost.php?p=81511449&postcount=403

Thanks in advance !

Regards !

Edit: I made a logcat from the system [MENTION=2010892]Nezorflame[/MENTION] Next step a logcat from boot / after rebooting. Maybe someone will do it or i will in next days
[Android Software Development] Nezorflame:
Is the second logcat the one which was taken on the 2nd boot? Since those files are different I'm not sure I understand which one is which.

Or are those two of the same first boot when everything was fine, and you are unable to take the one where you're stuck on bootlogo?