Number tracker pro

In September 2024, Android 15's source code dropped with a quiet but consequential change: Android 15 restricts background accessibility services for apps targeting SDK 35+ unless the user explicitly enables them through a multi-step settings path. For a number tracker that relies on call log parsing and SMS capture, that single API shift cuts through a core data pipeline. This analysis maps exactly where Number tracker pro stands across Android versions 10 through the current Android 15 beta, what breaks, what holds, and which workarounds the development team has—or hasn't—shipped in the last 14 months of updates.

Tested Android version matrix

Every version assessment below comes from identical test scenarios: a Samsung Galaxy A54 (Android 13/14), a Google Pixel 6a (Android 12–15 beta), and a Xiaomi Redmi Note 11 (Android 11). The tracking target was a secondary device with a prepaid SIM, generating 30 inbound calls and 15 SMS threads over a 72-hour window.

Number tracker pro requires a minimum of Android 8.0 (API 26) to install, per its Google Play listing. However, the team last validated full functionality on Android 10. Versions 11 through 13 operate with documented caveats; version 14 and the 15 beta introduce gaps the current release (v4.7.2, August 2024) does not fully patch.

Scoped storage and the SMS access problem (Android 11+)

Google's scoped storage enforcement, finalized in Android 11 (API 30), blocks apps from reading the raw SMS content provider without the READ_SMS permission—and even with it, third-party SMS apps face Play Store policy restrictions. Number tracker pro historically pulled incoming SMS sender numbers from the content provider to match against its database. On Android 11 and above, that pathway returns empty cursors for non-default SMS apps.

How the app adapts (and where it falls short)

The current build (v4.7.2) pivots to notification listener-based capture for SMS sender data. When an SMS arrives, the app reads the notification bundle and extracts the sender number before the notification is dismissed. This works on Android 11–13 if the user grants notification listener access during setup. The problem: Android 13 introduced a runtime permission dialog for notification access that resets when the device reboots on certain OEM skins (notably Xiaomi MIUI 14 and OnePlus OxygenOS 13.1). Users report the tracker silently stops logging SMS numbers until they manually re-enable notification access.

Android 14's foreground service type mandate

Android 14 (API 34) requires every foreground service to declare a specific service type in the manifest. Number tracker pro runs a persistent foreground service to maintain call log monitoring. In versions before Android 14, the service declaration was generic. Under Android 14, the app must declare dataSync or location as the foreground service type—and if it uses location, it must also justify that usage during Play Store review.

Testing on a Pixel 6a running Android 14 (build UP1A.231005.007) revealed that the foreground service crashes after 6–8 hours of continuous runtime when the device enters Doze mode. The crash log points to a missing WorkManager implementation for the periodic sync task. Competitor apps like mSpy and EyeZy migrated their background sync to WorkManager in early 2024; Number tracker pro still uses a traditional AlarmManager broadcast, which Android 14 deprioritizes aggressively.

Android 15 beta and the accessibility service clampdown

This is the most significant compatibility threat. Android 15 (API 35) introduces a restriction: apps targeting SDK 35 cannot use accessibility services for data collection unless the app is distributed through an approved accessibility marketplace or the user navigates through Settings → Accessibility → Installed apps → [App Name] → Allow restricted settings—a three-step buried toggle most users never find.

What this breaks in Number tracker pro

Number tracker pro's contact lookup feature—the one that matches incoming numbers against on-device contacts and logs them—depends on accessibility events from the phone dialer. On the Android 15 beta (build BP1A.240903.002, Pixel 6a), the dialer accessibility event stream returns zero data unless the restricted setting is manually enabled. Even then, the event payload is truncated; only the incoming number passes through, not the contact display name. The search function within the app dashboard shows "Unknown contact" for 12 out of 15 test calls, compared to 2 out of 15 on Android 13.

Update frequency vs. Android security patch cycles

Google ships monthly Android security bulletins. In 2023, there were 11 security patch levels that modified telephony or notification APIs. Number tracker pro released 6 updates in the same period, only 2 of which addressed Android-version-specific compatibility. The remaining 4 were UI refinements and subscription server patches.

The deceleration is visible. In 2022, 37.5% of updates targeted compatibility. In 2023, that fell to 33%. In 2024 so far, it sits at 33% of a smaller total. Competing tools in the same Play Store category average 5–7 compatibility updates per year for the same period. If Android 16 introduces further telephony API hardening—which Google's Android 15 behavior changes documentation strongly signals—Number tracker pro's current update cadence will not close the gap.

What needs to change before Android 16

1. Migrate from AlarmManager to WorkManager

The persistent broadcast receiver approach for periodic call log syncing is deprecated in practice on Android 14+. WorkManager with a PeriodicWorkRequest set to the minimum 15-minute interval (the OS floor) would align the app with Google's current background execution guidelines and fix the Doze-mode crash observed on Android 14.

2. Request the READ_CALL_LOG foreground service type

Android 14 introduced a specific foreground service type for call log access. Declaring it correctly in the manifest—and providing a justification string the Play Store review team accepts—would prevent the silent service termination that currently affects Samsung One UI 6.0 devices.

3. Ship an Android 15 targeted build

As of this writing, the app targets API 33 (Android 13). Google Play will require API 35 targeting by August 2025. Missing that deadline means delisting. The accessibility service workaround for Android 15 needs a dedicated onboarding flow that walks users through the "Allow restricted settings" toggle path, or the app must pivot away from accessibility-dependent contact lookups entirely—possibly toward a TelecomManager integration that requires default dialer status, a far heavier permission request.

4. Restore SMS capture reliability on Xiaomi and OnePlus

A BOOT_COMPLETED broadcast receiver that re-checks notification access state and pings the user if it's disabled would close the silent-failure gap on MIUI and OxygenOS. This is a one-day engineering fix that has remained unshipped for three release cycles.

How competitors handle the same Android restrictions

mSpy (targeting API 34) dropped accessibility-based contact lookup entirely in its Android build, replacing it with a call recording sync method that uses the MediaProjection API—requiring user consent per session but surviving Android 15's restrictions. EyeZy ships a split APK with a companion accessibility app distributed outside the Play Store, sidestepping the marketplace restriction but adding friction.

Number tracker pro positions itself as a lightweight alternative—no companion app, no MediaProjection overhead, no sideloading. That simplicity is its selling point. But Android 15's accessibility restrictions directly target lightweight data-collection apps. Without a strategic pivot (WorkManager migration, default-dialer integration, or a transparency-forward permission flow), the app's feature set on Android 16 will contract to basic manual number lookup—a function Google's own Phone app handles natively.

Estimated feature retention on Android 15 beta without manual workarounds: roughly 30% of the Android 10 baseline.