All applications crashing (foreground)

[Jake_R]

Over the last 3-4 weeks, I've had applications crashing in the foreground, normally Pokemon Go. When this happens, all the apps crash and I'm returned to the home screen. After doing some digging with adb/logcat, I've found this error:

02-25 20:14:09.736 1856 10366 I ActivityManager: Too many PendingIntent created for uid 10150, pendingIntentRecordendingIntentRecord{3ac0c70 com.google.android.gms broadcastIntent}
02-25 20:14:09.737 1856 10366 I ActivityManager: incrementUidStatLocked count:5000
02-25 20:14:09.737 1856 10366 I ActivityManager: kill process:com.google.android.gms for too many pendingintentrecord
02-25 20:14:09.807 1856 2159 I ActivityManager: Force stopping com.google.android.gms appid=10150 user=-1: too many pendingintentrecord

uid10150 is Google Play Services, the same one which is complaining about too many pending intent records (alarms/notification, I think?).

Just prior to this happening, I can see a bunch of messages about "SensorService" and "AlarmManager" which may be related; see below. Anyone know what's going on here? The crashes are fairly erratic and don't seem to care how long the app has been running. I've removed updates from Google Play services and cleared its app data but the error is still happening.
Phone is a Realme 7 pro (RMX2170) running Android 10 and latest updates.

02-25 20:14:07.399 1856 4649 V AlarmManager: set(PendingIntent{107fad3: PendingIntentRecord{1044610 com.google.android.gms broadcastIntent}}) : type=3 when=1611405692whenElapsed1611405692m
axWhen =1611405692 win=0 interval=0 flags=0x0 pkg = com.google.android.gms
02-25 20:14:07.662 1856 1856 D OppoPowerMonitor: Receive broadcast android.intent.action.BATTERY_CHANGED
02-25 20:14:08.289 1856 4024 I GnssLocationProvider: Total SV info received at framework: 74.
02-25 20:14:08.427 1856 5072 V AlarmManager: set(PendingIntent{acfb33c: PendingIntentRecord{f73c8c5 com.google.android.gms broadcastIntent}}) : type=3 when=1611406695whenElapsed1611406695m
axWhen =1611406695 win=0 interval=0 flags=0x0 pkg = com.google.android.gms
02-25 20:14:08.732 1856 10366 W SensorService: SensorEventConnection sensor handle=11, package = com.google.android.location.collectionlib.SensorScanner$SensorEventListenerAdapter disable
02-25 20:14:08.732 1856 10366 D SensorService: recordConnection in disable
02-25 20:14:08.732 1856 10366 D SensorService: SensorDevice::activate: ident=0x7d45906200, handle=0x0000000b, enabled=0, count=6
02-25 20:14:08.732 1856 10366 D SensorService: disable index=4
02-25 20:14:08.733 1856 10366 D SensorService: >>> actuating h/w batch 0x0000000b 10000000 0
02-25 20:14:08.735 1856 10366 D SensorService: 12 active sensors
02-25 20:14:08.735 1856 10366 D SensorService: removing connection 0x7d45906200 for sensor[0].handle=0x0000000b
02-25 20:14:08.735 1856 10366 D SensorService: removing connection 0x7d45906200 for sensor[1].handle=0x00000015
02-25 20:14:08.736 1856 10366 D SensorService: removing connection 0x7d45906200 for sensor[2].handle=0x00000029
02-25 20:14:08.736 1856 10366 D SensorService: removing connection 0x7d45906200 for sensor[3].handle=0x0000005b
02-25 20:14:08.736 1856 10366 D SensorService: removing connection 0x7d45906200 for sensor[4].handle=0x00000065
02-25 20:14:08.736 1856 10366 D SensorService: removing connection 0x7d45906200 for sensor[5].handle=0x0000006f
02-25 20:14:08.736 1856 10366 D SensorService: removing connection 0x7d45906200 for sensor[6].handle=0x0000008d
02-25 20:14:08.736 1856 10366 D SensorService: removing connection 0x7d45906200 for sensor[7].handle=0x000000a1
02-25 20:14:08.736 1856 10366 D SensorService: removing connection 0x7d45906200 for sensor[8].handle=0x000000bf
02-25 20:14:08.736 1856 10366 D SensorService: removing connection 0x7d45906200 for sensor[9].handle=0x000000de
02-25 20:14:08.736 1856 10366 D SensorService: removing connection 0x7d45906200 for sensor[10].handle=0x0000010f
02-25 20:14:08.736 1856 10366 D SensorService: removing connection 0x7d45906200 for sensor[11].handle=0x000003e9
02-25 20:14:08.739 1856 10366 D SensorService: ~SensorEventConnection(0x7d45906200)
02-25 20:14:08.785 1856 10366 V AlarmManager: set(PendingIntent{8d6b21a: PendingIntentRecord{68dfb5c com.google.android.gms broadcastIntent}}) : type=2 when=1611400167whenElapsed1611405168m
axWhen =1611405168 win=0 interval=0 flags=0x0 pkg = com.google.android.gms
02-25 20:14:09.290 1856 4391 I GnssLocationProvider: Total SV info received at framework: 72.
02-25 20:14:09.443 1856 5078 V AlarmManager: set(PendingIntent{a153ec3: PendingIntentRecord{1fd5340 com.google.android.gms broadcastIntent}}) : type=3 when=1611407695whenElapsed1611407695m
axWhen =1611407695 win=0 interval=0 flags=0x0 pkg = com.google.android.gms
02-25 20:14:09.451 1856 3994 V AlarmManager: set(null) : type=2 when=1611410831whenElapsed1611410831maxWhen =1611410831 win=0 interval=0 flags=0x8 pkg = android
02-25 20:14:09.454 1856 10366 W SensorService: SensorEventConnection sensor handle=11, package = com.google.android.location.collectionlib.SensorScanner$SensorEventListenerAdapter enable
02-25 20:14:09.454 1856 10366 D SensorService: Calling batch handle==11 flags=0rate=20000000 timeout== 0
02-25 20:14:09.454 1856 10366 D SensorService: SensorDevice::batch: ident=0x7d45906200, handle=0x0000000b, flags=0, period_ns=20000000 timeout=0
02-25 20:14:09.454 1856 10366 D SensorService: >>> curr_period=10000000 min_period=10000000 curr_timeout=0 min_timeout=0
02-25 20:14:09.454 1856 10366 D SensorService: >>> actuating h/w flush 11
02-25 20:14:09.454 1856 10366 D SensorService: recordConnection in enable
02-25 20:14:09.454 1856 10366 D SensorService: Calling activate on 11
02-25 20:14:09.454 1856 10366 D SensorService: SensorDevice::activate: ident=0x7d45906200, handle=0x0000000b, enabled=1, count=6
02-25 20:14:09.454 1856 10366 D SensorService: enable index=4
02-25 20:14:09.456 1856 3000 D SensorService: flush complete event sensor==11
02-25 20:14:09.457 1856 3000 D SensorService: flush complete event sensor==11
02-25 20:14:09.457 1856 3000 D SensorService: First flush event for sensor==11
02-25 20:14:09.457 1856 3000 D SensorService: flush complete event sensor==11
02-25 20:14:09.670 1856 4649 V AlarmManager: set(PendingIntent{b855422: PendingIntentRecord{7a3d7df com.google.android.gms broadcastIntent}}) : type=2 when=1611406052whenElapsed1611406053m
axWhen =1611406053 win=0 interval=0 flags=0x0 pkg = com.google.android.gms
02-25 20:14:09.720 1856 5072 V AlarmManager: set(PendingIntent{bb35eb3: PendingIntentRecord{7a3d7df com.google.android.gms broadcastIntent}}) : type=2 when=1611406052whenElapsed1611406104m
axWhen =1611406729 win=625 interval=0 flags=0x0 pkg = com.google.android.gms
02-25 20:14:09.457 1856 3000 D SensorService: flush complete event sensor==11
02-25 20:14:09.724 1856 10366 D OppoNlpProxy: OppoNlpProxy onlocation changed!!

 

[puppykickr]

Have you tried restarting the device?

Also, have you enough open memory to use the apps that you are trying to use?
A good rule of thumb is to leave at least as much open memory as the phone has RAM.

 

[Jake_R]

Yes, tried restarting, same thing within the same timeline as simply restarting the app. The phone has 8GB RAM, looking at RAM Truth, I can see 4680MB active, 2871MB available so it doesn't seem to be memory constraints. What do you mean by "open memory"?

 

[mikedt]

Have you tried starting the phone in safe mode, and see if things are still crashing then? You could try a factory reset, in case something in the software is just messed-up.

Realme, I believe that's a brand of Oppo. I've had Oppo phones before, and some versions of their Color OS "based on Android" can be buggy.

 

[puppykickr]

Yes, tried restarting, same thing within the same timeline as simply restarting the app. The phone has 8GB RAM, looking at RAM Truth, I can see 4680MB active, 2871MB available so it doesn't seem to be memory constraints. What do you mean by "open memory"?

By 'open memory', I am referring to the internal memory that you have access to.

Meaning the space that is left over besides the system that you can use for apps, media, whatever.

This is partially why it is important to keep your media (pictures, videos, PDF files, etc. stored on a SD card instead of the internal memory.

What is the capacity of the processor?
For instance, I have two devices that each have 1GB processors, and two others that each have 2GB processors.

On the 1GB devices, I make sure to leave at least 1GB of open memory available so that the apps can have a cache and some room to work.

Likewise, I leave at least 2GB available for the same reasons on the 2GB devices.

Why?
More apps can run simultaniously on the 2GB devices.

A good rule of thumb is to try to keep your internal memory to 70% or less full.

My sister has a phone much more powerful than mine, yet she has endless problems with it.

I checked it, and her internal memory is 99% full on a 64GB device!
No wonder she is having issues with it!

I am just trying to see if you are in the same boat as she is, and if that could be causing your troubles.

Try this simple app to see where you are at...

https://f-droid.org/en/packages/com.kgurgul.cpuinfo/

The app is small, and is very easy to navigate.

 

[puppykickr]

Notice how the device is an '8GB' device, yet I only have access to 4.13GB?

That is because the system takes up that much space.

The processor on this device is only 1GB, which is dismal by today's standards, but I can maintain decent functionality by keeping my memory useage below 70%, as you see in the screenshot.

This device has around 1½GB of empty internal space, at the moment.

Even at that, certain apps can and will crash sometimes.

That is due to other things- it is called a 1GB processor, but it is actually less than that.

It is an old, inefficient OS, and has a relatively high threshold, which is the minimum open portion of that (less than) 1GB that can be used before the thing will freeze up/crash.

 

[puppykickr]