[Android] Firestore snapshot listeners is slow to retrieve data.

### Version info

**Angular:** 17.3.3

**Firebase:** 10.10.0

**AngularFire:** 17.0.1

**Other (e.g. Ionic/Cordova, Node, browser, operating system):**
Ionic:

Ionic CLI : 7.2.0 (/Users/user/.nvm/versions/node/v18.17.0/lib/node_modules/@ionic/cli)
Ionic Framework : @ionic/angular 7.8.2
@angular-devkit/build-angular : 17.3.2
@angular-devkit/schematics : 17.3.2
@angular/cli : 17.3.2
@ionic/angular-toolkit : 11.0.1

Capacitor:

Capacitor CLI : 5.7.4
@capacitor/android : 5.7.4
@capacitor/core : 5.7.4
@capacitor/ios : 5.7.4

Utility:

cordova-res : not installed globally
native-run : 2.0.1

System:

NodeJS : v18.17.0 (/Users/user/.nvm/versions/node/v18.17.0/bin/node)
npm : 10.5.0
OS : macOS Unknown

### How to reproduce these conditions

**Failing test unit, Stackblitz demonstrating the problem**

**Steps to set up and reproduce**

We have developed an Ionic Hybrid app for iOS, Android, and Web platforms, which has been functioning smoothly for the past two years. However, after multiple library updates, we have encountered an issue specific to Android devices. Retrieving the first fresh snapshot listener takes an exceptionally long time on Android, whereas iOS and web platforms retrieve the same snapshot listener in just 1 second on the same device. Android hybrid apps may take up to 60 seconds for this process.

Interestingly, restarting the app after the initial retrieval significantly improves the speed.

I am currently using the compat SDK instead of the Web modular SDK. I wonder if this choice affects the result.

**Sample data and security rules**

### Debug output

** Errors in the JavaScript console **

** Output from `firebase.database().enableLogging(true);` **

** Screenshots **

### Expected behavior

### Actual behavior

Comece reproduzindo o primeiro listener de snapshots do Firestore no Android usando as versões listadas de Angular, Firebase, AngularFire, Ionic e Capacitor, comparando-o com iOS e web. Verifique se o compat SDK afeta o atraso e o momento da captura ou a saída de depuração; considera-se concluído quando a lentidão específica do Android está explicada e uma correção verificada ou um encaminhamento claro para o upstream está documentado.

Escrita pelo modelo de indexação a partir do texto da issue.