ANR Report Observed in Logs While App Runs Fine on Device

Vega Open Beta Q&A
1

Hii Vega Team,

We are observing an ANR (App Not Responding) crash report for our Fire TV application in Vega Simulator logs and Fire TV system crash reports.

CrashDescriptor:cb9997c0f3205bfa089260eb594c158e
CrashLang:Native
Process:com.abp.firetv
LibraryName:N/A
CrashReason:AppNotResponding
CrashTimeUTC:1768484000000
OsBuildNumber:1402060343030
SystemVersion:1.0.50343.0(9a1d8dfa7da5d600)/10503430N:user/dev-keys
BuildVariant:user
FullUnwind:true
DumpSuccess:true
AppVersion:2.0.0
AppBuildNumber:0
hasForegroundActivities:False

<acr_meta_info>
UPTIME_SECONDS:4224
PROCESS:com.abp.firetv
LIBRARY_NAME:N/A
LCM_KILLREASON: AppNotResponding
LCM_KILLTIME: 1768484000360
LCM_APP_IN_FOREGROUND: false
LCM_ANR_REASON: App Launch Failed (Error on Callback)
LCM_APPS_IN_FOREGROUND_WHEN_CRASHED:
displayId: 0 appId: com.abp.firetv.main instId: 1175
PRODUCT_NAME:vvrp-tv-arm64
CRASH_DATE:Thu Jan 15 13:33:20 2026
</acr_meta_info>
<pressure_info>
<cpu_pressure>
some avg10=11.97 avg60=11.53 avg300=11.08 total=433882745
full avg10=0.00 avg60=0.00 avg300=0.00 total=0
</cpu_pressure>
<io_pressure>
some avg10=0.78 avg60=0.22 avg300=0.08 total=6075442
full avg10=0.51 avg60=0.15 avg300=0.05 total=3604045
</io_pressure>
<memory_pressure>
some avg10=0.00 avg60=0.01 avg300=0.01 total=199609
full avg10=0.00 avg60=0.01 avg300=0.00 total=141978
</memory_pressure>
</pressure_info>

MemTotal: 4025104 kB
MemFree: 288264 kB
MemAvailable: 823684 kB
Buffers: 34012 kB
Cached: 1810628 kB
SwapCached: 0 kB
Active: 486416 kB
Inactive: 976004 kB
Active(anon): 254640 kB
Inactive(anon): 648276 kB
Active(file): 231776 kB
Inactive(file): 327728 kB
Unevictable: 1026972 kB
Mlocked: 2596 kB
SwapTotal: 0 kB
SwapFree: 0 kB
Dirty: 1012 kB
Writeback: 0 kB
AnonPages: 644752 kB
Mapped: 328352 kB
Shmem: 1282540 kB
KReclaimable: 46992 kB
Slab: 127220 kB
SReclaimable: 46992 kB
SUnreclaim: 80228 kB
KernelStack: 21048 kB
PageTables: 27736 kB
SecPageTables: 0 kB
NFS_Unstable: 0 kB
Bounce: 0 kB
WritebackTmp: 0 kB
CommitLimit: 2012552 kB
Committed_AS: 11842604 kB
VmallocTotal: 259653632 kB
VmallocUsed: 30484 kB
VmallocChunk: 0 kB
Percpu: 3792 kB

Key observations:

  • Crash Reason: AppNotResponding

  • ANR Reason: App Launch Failed (Error on Callback)

  • The app is reported as not in foreground at the time of kill.

  • CPU, memory, and IO pressure levels are within normal limits.

  • The crash occurs during the app launch phase according to system logs.

Important note:
When we test the application manually on:

  • Fire TV device

  • Vega Simulator (UI testing)

The application launches and runs correctly without any visible issues or freezes.

3

874#crash_1768493686_30037_5000_5668_13567233_com_abp_firetv.acr (287.5 KB)
This is the crash report
PFA
Thankyou

4

Hi @ABP_Network,

Thank you for the detailed ANR crash report and the comprehensive technical information you’ve shared.

I can see that you’re observing an ANR (App Not Responding) crash in the Vega Simulator logs with the reason “App Launch Failed (Error on Callback)”, even though the application launches and runs correctly when tested manually on both Fire TV devices and the Vega Simulator UI.

Our team is investigating this issue and will provide an update as soon as we have more information. The fact that the app works fine during manual testing but shows ANR reports in the logs is particularly interesting and will help us in our investigation.

Thanks for helping us improve the Vega platform.

Warm regards,
Aishwarya

5

Hi @ABP_Network,

Our team has analyzed the ANR crash report. This appears to be a background crash that may involve supporting services rather than your main app, which explains why it runs fine during testing.

Could you please provide:

  • Device logs captured during the crash time window (ideally a few minutes before and after)

  • Any information about what actions or events preceded the crash

  • Details about any background services or interface services your app uses

This will help us identify what triggered the issue. Thanks for your help!

Warm regards,
Aishwarya

6

Hii team,
This issue has been resolved. Thank you for your support.