Gmscore: Cannot add a Google account ('Just a sec...')

[olliejm]

I have just installed the latest nightly of LineageOS, and the microG suite (via F-Droid repository) on a OnePlus3T.

However, if I try to add a Google account in settings -> accounts, the page never loads. It just has the 'Just a sec...' loading screen indefinitely.

I installed Play Store, and the same thing happens.

I have disabled AdAway, rebooted, and given microG gmscore every permission available.

[JonnyTech]

If you are on the latest nightly, ie the 14.1 branch, then you need to copy GmsCore.apk to /system/priv-app/

[olliejm]

Yeah this worked, thanks!

[YogliB]

Doesn't work for me... I downloaded the file and moved it there, then rebooted.

I'm using RR v5.8.3 (Android 7.1.2) on a Xiaomi Mi 4c.

[billop]

This is also not working for me, which means that I can't use calendar or google drive backup for SMS Backup. I am on 7.1.2 omni rom, using the latest fdroid release apk on Sony Xperia X Compact.

[billop]

Just installed the latest release (relased today lol) and everything is working well.

[teoman002]

I need some help with the same issue too!
When I try to add a Google account, it says "wait a sec", but doesn't continue.
I downloaded the last gmscore.apk and put it in the priv-app folder.
Furthermore I gave it root permissions via the file manager.
The following apps are running on my system and could prevent my system connect to the Internet. Is there a way to check that? Maybe cloud messaging check could prove the problem.

xposed, xprivacy (gms has full permissions) and Afwall (firewall) (here I only have gms proxy to choose from)

[pomarec]

Based on this commit description, it should have been fixed
@UnicodeAlt255 Do you know where we can find a compiled apk of the last version ? It seems that the last release is 0.2.4.

[ale5000-git]

@pomarec: The latest version is always here, use the drop down menu.

[pomarec]

@ale5000-git My bad, I did not see that. Works like a charm, thanks.

[ale5000-git]

@transiti0nary
If you have fixed your problem close the issue please.

@YogliB @teoman002
Have you fixed your problems?

[teoman002]

the last version and permission updates fixed my problem.

[haunma]

Please let me know if I should open a new issue, but because I am having the exact same problem (stalls on "Just a sec..."), and this issue is still open, I'm posting my report here.

I'm running the latest microG components from the F-Droid repository on a Nexus 10 tablet with a Marshmallow ROM supporting signature spoofing (OmniROM). In the microG settings app, all of the self checks are passing.and I've enabled "device checkin" and GCM from the settings page too. My NLP provider (LocalWifi backend) is working correctly, and I get valid location in, e.g. Google Maps.

What I cannot do, is add or sign in to a google account. I have the symptoms described in this issue, i.e. Settings->Accounts->Add account->Google results in the white screen with "Just a sec..." and the rolling progress bar. This continues indefinitely. Logcat during this time:

`
I/ActivityManager( 477): START u0 {act=com.android.systemui.recents.SHOW_RECENTS flg=0x10804000 cmp=com.android.systemui/.recents.RecentsActivity} from uid 10016 on display 0

D/mali_winsys( 686): new_window_surface returns 0x3000

D/mali_winsys( 2210): new_window_surface returns 0x3000

I/ActivityManager( 477): START u0 {act=android.settings.ADD_ACCOUNT_SETTINGS cmp=com.android.settings/.accounts.AddAccountSettings (has extras)} from uid 1000 on display 0

I/ActivityManager( 477): START u0 {cmp=com.android.settings/.accounts.ChooseAccountActivity (has extras)} from uid 1000 on display 0

D/mali_winsys( 2210): new_window_surface returns 0x3000

I/ActivityManager( 477): Displayed com.android.settings/.accounts.ChooseAccountActivity: +163ms (total +184ms)

D/OpenGLRenderer( 2210): endAllStagingAnimators on 0xb82fa1b8 (ListView) with handle 0xb81002d0

D/AudioFlinger( 228): mixer(0xb4693008) throttle end: throttle time(11)

D/mali_winsys( 2210): new_window_surface returns 0x3000

D/mali_winsys( 2210): new_window_surface returns 0x3000

I/ActivityManager( 477): START u0 {cmp=com.google.android.gms/org.microg.gms.auth.login.LoginActivity (has extras)} from uid 1000 on display 0

W/cr_AwContents( 914): onDetachedFromWindow called when already detached. Ignoring

D/mali_winsys( 914): new_window_surface returns 0x3000

I/cr_Ime ( 914): ImeThread is not enabled.

I/ActivityManager( 477): Displayed com.google.android.gms/org.microg.gms.auth.login.LoginActivity: +151ms

D/OpenGLRenderer( 2210): endAllStagingAnimators on 0xb84b2d68 (ListView) with handle 0xb83807d8

W/cr_BindingManager( 914): Cannot call determinedVisibility() - never saw a connection for the pid: 914

D/GmsAuthLoginBrowser( 914): pageFinished: https://accounts.google.com/EmbeddedSetup?source=android&xoauth_display_name=Android%20Device&lang=en&cc=us&langCountry=en_us&hl=en-US&tmpl=new_account

W/cr_BindingManager( 914): Cannot call determinedVisibility() - never saw a connection for the pid: 914

W/cr_BindingManager( 914): Cannot call determinedVisibility() - never saw a connection for the pid: 914

D/GmsAuthLoginBrowser( 914): pageFinished: https://accounts.google.com/EmbeddedSetup?source=android&xoauth_display_name=Android%20Device&lang=en&cc=us&langCountry=en_us&hl=en-US&tmpl=new_account

D/GmsAuthLoginBrowser( 914): pageFinished: https://accounts.google.com/EmbeddedSetup?source=android&xoauth_display_name=Android%20Device&lang=en&cc=us&langCountry=en_us&hl=en-US&tmpl=new_account

W/cr_BindingManager( 914): Cannot call determinedVisibility() - never saw a connection for the pid: 914

W/cr_BindingManager( 914): Cannot call determinedVisibility() - never saw a connection for the pid: 914

D/GmsAuthLoginBrowser( 914): pageFinished: https://accounts.google.com/EmbeddedSetup/identifier?source=android&xoauth_display_name=Android%20Device&lang=en&cc=us&langCountry=en_us&hl=en-US&tmpl=new_account&flowName=EmbeddedSetupAndroid

I/chromium( 914): [INFO:CONSOLE(1)] "'webkitIDBCursor' is deprecated. Please use 'IDBCursor' instead.", source: (1)
`

Possibly worth mentioning: I am attempting to use google's play store app, rather than blankstore or fakestore. I installed the patched version of the apk from shadow53.com (via recovery). It was working fine for me on another device, although that one was LineageOS 14.1 with microG built in. But I don't think this is the cause of the account-add failure...?

Someone mentioned moving GmsCore.apk to /system/priv-app, but this is Marshmallow and AFAICT the default installation from F-Droid was working fine for everyone during that era, so I haven't tried this. (Actually, I don't know how!)

Battery optimization is disabled for MicroG core service, and I believe all of the relevant permissions have been granted.

[haunma]

My apologies. I did not have the latest version of microG installed after all. It's actually quite difficult to be sure of this when you install from F-Droid, as if you mistakenly install the stable version before enabling expert mode and unstable updates, F-Droid will insist that you do in fact have the latest, and nothing else is compatible. To see the snapshot/unstable versions then, you have to first uninstall. Just mentioning this here in case others are similarly confused. I read all of the comments and was still certain that I had the correct version. Wrong!

With the latest snapshot I was able to add a google account and sign in. Still having problems with the google play store (patched version from shadow53.com) crashing on start due to a permissions issue on libcronet. I'm pursuing that with the zip package maintainer as it's not a microG issue per se.