Map doesn't show in App because "Google Play services are updating"

fid02

Yes, doesn't look like it's exclusive to EOL devices.

Takamasa

I also got the same issue on pixcel 4a. Hope this will be fixed soon.

muhomorr

m00ninite Do send the logs. I still haven't received logs from anybody and am unable to reproduce this issue.

bla

Hello;

I have the same issue with my pixel 4a and the app citymapper.
Uninstalling and installing Google play services works for a few minutes/ hours.

As well erasing all thé user data and cache of Google play services.

I would like to send the logs but i dont have this option; altough my graphene os version seems up to date : what can i do to send to you?
Thank you!!
Kernel :
4.14.302-g4d19a21e7fa7
#1 Thu 01 Jan 1970 12:00:00 AM UTC
Build number
TQ3A.230805.001.S1.2024080800

fid02

bla I would like to send the logs but i dont have this option;

What do you mean you don't have the option? Have you tried to do as muhomorr instructed?

Сapture it after reproducing this issue by going to Settings -> System -> View logs -> Share (or Save).

'Settings' refers to the Settings app.

de0u

bla I have the same issue with my pixel 4a [...]

I would like to send the logs but i dont have this option; altough my graphene os version seems up to date : what can i do to send to you?

I think the easy exporting of system logs may be an addition to GrapheneOS on Android 14, and I think 4a devices may be frozen on A13.

bla

[url=https://img.tedomum.net/data/Screenshot_20240915-140308-d00342.png][img]https://img.tedomum.net/data/thumb/Screenshot_20240915-140308-d00342.png[/img][/url]

I mean i dont see it!

fid02

bla The System Log viewer can only be accessed from the Owner profile (main profile).

Incidentally, if you disable Developer options and reboot the device, does the problem persist?

bla

fid02

I have only a main profil; and i activated developper option because i didn't see the log before - and i still dont see it :)

kdf

There is no view logs option in settings/system

bla

de0u
Possible because i seem up to date; and i am un Android 13...

de0u

de0u I think the easy exporting of system logs may be an addition to GrapheneOS on Android 14, and I think 4a devices may be frozen on A13.

bla Possible because i seem up to date; and i am un Android 13...

Please note that the GrapheneOS project stated "Pixel 4, Pixel 4 XL and Pixel 4a are end-of-life and shouldn't be used anymore due to lack of security patches for firmware and drivers" nearly a year ago (source). My understanding is that the primary goal of extended support is to somewhat increase the safety of EOL devices while users work out a transition plan to a newer device.

I no longer have an A13 device so I don't recall how to find system logs. Perhaps somebody else here does.

therehelog

Hi, i think that this could be related to another problem, some days ago i noticed that the qrcode scanning function on 2 unrelated banking apps stopped working, qrcode scanning works fine using the camera app and on some other apps like whatsapp and telegram, i tried all the suggestions/checks that i found on the internet but none of them worked
(like enable camera permissions on all google services apps if present).

Now i noticed that there was this problem too for map visualization, i cleaned the cache and data of google services and the qrcode worked for a few seconds.

So i think that they could be related but it's difficult to test because after a few seconds the problem starts again, could someone else please check qrcode scanning for some apps to see if you have the same problem?, thanks.

Upstate1618

Hey I encountered the same issue in one of my apps and toggling DCL to enabled works for me. It seems a DCL problem with apps. You can enable compatibility mode for the app first to see if it works.

GrapheneOS

Upstate1618 DCL storage restrictions are not enabled by default and show a clear notification when code loading is prevented. Play services dynamite modules are partially incompatible with DCL restrictions until they fully move them to split APKs. That's a known incompatibility. You should not enable exploit protection compatibility mode to work around this but rather don't enable the DCL storage restrictions for apps requiring it. You shouldn't disable the standard memory exploit protections.

other8026

I thought that the log viewer was around for longer than it has been, apparently.

You can get logs by following these instructions: https://developer.android.com/studio/debug/bug-report#bugreportdevice

matchboxbananasynergy

This should be solved with the upcoming GrapheneOS release.

the0815

matchboxbananasynergy will the release that contains this fix also come to devices with legacy extended support (like 4a, 4XL) that multiple people reported the problem on in this thread?

matchboxbananasynergy

the0815 Almost certainly not. Those devices are in legacy extended support and are very much on their way out. We've been at the point where people on these devices need to update to a support model for quite a while now.

« Previous Page Next Page »