Confused About Google Prompt (login) and /e/OS

Using /e/OS Applications
1

Please help me place this in the correct/better sub-forum if needed.

My device is an Android Moto-G7 with /e/OS. When I go to login to my Google email or Voice account via PC/browser, Google sometimes requires me to check my “Google Pixel 2” phone for a login prompt. I don’t have (and have never had) a Pixel, and no login prompt appears on my Moto-G7.

Google tells me the Pixel-2 was added to account 287 days ago, which is exactly the time frame I installed /e/OS on my Moto-G7

Does /e/OS have a place where a “spoofed” phone model can be selected, i.e. did I do something to tell Google I have a Pixel-2 rather than a Moto-G7?

microG disguising as Google Pixel 2 (in 2025!)
2

that should be a microG setting (or cromite?) - in any case, the phone can’t confirm those Google Prompts. You’d need to setup regular OTP in an authenticator to do this with the phone.

1 Like
3

Thanks. But what I am trying to understand is why official Google account thinks the phone is a Pixel-2 when it’s not.

4

So, unused here, but you might check

Settings > MicroG >

  • Google accounts
  • Google device registration

… but on Moto G7 Power ocean, Pixel 2 seems not an option.

5

Thanks for getting me into that area. My “Google device registration” is, and I assume has been, “Automatic: Native”.

There is a choice for “Motorola Moto G (Lineage OS)” that I am tempted to try.

Reminder, my main goal is for when Google arbitrarily decides to use phone prompt to validate a login attempt, I actually receive the prompts to my phone (which isn’t currently the case).

6

Well try it then … this is (imho) correct.

It is not said where this definition is generated – it is oddly non specific.

Native: “belonging by birth” or so.

7

that took some digging, there’s this warning when you add a Google account

Murena will report a fake device model to Google to protect your privacy. You can check which one on Google’s Device Activity after you log in

haven’t looked up how user-agent-reduction works, for later

2 Likes
8

That’s some pretty impressive sleuthing…thanks.

9

in any case, the phone can’t confirm those Google Prompts

had another look at status of this, there were 2 issues tracking it and I looked at the duplicate one.

This got merged end of July and made it into the 0.3.9 microg release: Auth: Support Google 2-step verification by DaVinci9196 · Pull Request #2866 · microg/GmsCore · GitHub

and got enabled by default for /e/OS v3.3 here - microG: activate 2FA (ad036739) · Commits · e / os / android_prebuilts_prebuiltapks_lfs · GitLab until then it needs the flip here to use:

screenshot

Settings → System → microG → Google Accounts → (bottom) “Receive two-step verification ..”

Screenshot_20251116-102151_microG Services_600x1200-q85
Screenshot_20251116-102151_microG Services_600x1200-q85600×1200 71.6 KB

2 Likes
Buying an app through Google Play, but cannot succeed Google Identification due to wrong smartphone
10

Thanks! My setting was off, and I have toggled it “on”. I’m hoping this clears it up (for now).

Oddly/unexpectedly, that “Receive two-step verification” toggle button is purple instead of white (off) or green (on). Not sure what that indicates or if that has any significance with respect to this issue?

11

Quick update…Google sent me a 2FA request to my phone this a.m., and when I checked phone, it was there! And responded correctly/as desired to my “Yes” tap. So changing this setting as indicated above worked for me. Hooray.

12

great. Sure is convenient for those who have their Google Account added anyway.

But I’d still add an alternative 2SV method for when Google Prompts breaks. The phone number isn’t an ideal fallback, TOTP and passkeys are more transferable than a SIM and not bound to a contract.

13

This topic was automatically closed after 90 days. New replies are no longer allowed.