Android Question AppName not responding

LucasHeer · 2026-03-28T11:36:29+0000

Starting this morning, every B4A app that I compile (debug & release) to my phone, will randomly throw "AppName is not responding." even though the UI thread is still fully responsive. Clicking "Wait", allows me to use the app for another 20-30 seconds until the message comes up again. There are no errors in the logs.

This seems to only happen on my phone, over both USB or WIFI debugging:

Pixel 9 Pro
Android 16

I tested another another device, TLC 9183W Android 12 with no issue at all.

Could it be my phone? I restarted and checked for updates, and 30GB of storage available. I checked the unfiltered logs, and no clue to why this may be happening.

Thank you!!

LucasHeer · 2026-03-28T14:04:17+0000

I tried a different PC with B4A installed, debugging to the Pixel 9 Pro — Same issue.

I tried to factory resetting the android device (Pixel 9 Pro) — Same issue as well.

Is it possible that this problem is related to the newest Android update? The problem still occurs with a brand new B4XPages example app.

Sagenut · 2026-03-28T14:33:39+0000

Which Android version is installed on the Pixel?
Are you using the latest B4A version?

LucasHeer · 2026-03-28T16:49:25+0000

Sagenut said:
Which Android version is installed on the Pixel?
Are you using the latest B4A version?

Hey sir!

Android 16
Build: CP1A.260305.018

And yes sir, B4A 13.40

It's very weird, I feel like it has to be the newest Android update. I use B4A almost daily, and it started happening this morning. On several PCs with B4A, and factory reset phone.

The UI never stalls, and I click click "Wait" and the app is fine. But this message comes up every 30-40 seconds. This is for any B4A project, even an empty example project.

My dad has the same Pixel 9 pro, I am going to ask him if I can test on his phone later

LucasHeer · 2026-03-28T23:02:29+0000

I installed a fresh copy of B4A 13.40 on my dad's PC.

He also has a Pixel 9 Pro, Android 16, Build CP1A.260305.018, -- Same exact issue.

When running B4A.Example, it gives a "AppName not responding" message every 40-50 seconds.

What could be causing this? I can develop around this, but not sure that I want to put out an app update like this.

Thank you!!

Sagenut · 2026-03-28T23:19:26+0000

If possible I would suggest to create an emulator with Android 16.
To check if the problem is exclusively related to the Pixel in some way.

LucasHeer · 2026-03-28T23:27:05+0000

Sagenut said:
If possible I would suggest to create an emulator with Android 16.
To check if the problem is exclusively related to the Pixel in some way.

I've had Android 16 for quite some time, I bet it is pixel related or newest build. I will definitely try an Android 16 emulator though!

Thank you!

Edit: I think I am going to unlock my bootloader and rollback update and try that too.

But even release builds are causing this issue right now, I'm wondering if my customers will experience this?

LucasHeer · 2026-03-29T00:16:15+0000

Sagenut said:
If possible I would suggest to create an emulator with Android 16.
To check if the problem is exclusively related to the Pixel in some way.

Hey sir! I tried on a Pixel 9 Pro emulator running Android 17. It runs perfect!

It looks like I can join Android 17 beta for my phone, do you think this would be a bad idea for currently version of B4A?

Edit: Same issue with Android 17 beta, tried 3 computers with B4A 13.4 and B4A.Example

PaulMeuris · 2026-03-29T04:25:02+0100

It is probably device related...

Erel · 2026-03-29T08:11:50+0100

Check the logs including the unfiltered logs. There should be more information there.

You can use adb: https://www.b4x.com/android/forum/threads/monitoring-the-unfiltered-logs-for-errors.168727/#content

Sandman · 2026-03-29T14:38:05+0100

I was JUST about to create my own post, identical to this with the difference being that I have a Pixel 7 (Also Android 16). I'll try adding by info here, as it sounds we might be bitten by the same bug. (If asked, I will create a new thread.)

Erel said:
Check the logs including the unfiltered logs. There should be more information there.

You can use adb: https://www.b4x.com/android/forum/threads/monitoring-the-unfiltered-logs-for-errors.168727/#content

I have, lots and lots - using guiding from Claude. Everything points to Starter being my issue, but the thing is that the Starter isn't edited in any way. Here it is:

Starter:

#Region  Service Attributes
    #StartAtBoot: False
    #ExcludeFromLibrary: True
#End Region

Sub Process_Globals
    'These global variables will be declared once when the application starts.
    'These variables can be accessed from all modules.

End Sub

Sub Service_Create
    'This is the program entry point.
    'This is a good place to load resources that are not specific to a single activity.

End Sub

Sub Service_Start (StartingIntent As Intent)
    Service.StopAutomaticForeground 'Starter service can start in the foreground state in some edge cases.
End Sub

Sub Service_TaskRemoved
    'This event will be raised when the user removes the app from the recent apps list.
End Sub

'Return true to allow the OS default exceptions handler to handle the uncaught exception.
Sub Application_Error (Error As Exception, StackTrace As String) As Boolean
    Return True
End Sub

Sub Service_Destroy

End Sub

In my case this happens while the app is just idling and doing nothing. I have extensive logging available in the app so I'm certain it doesn't do anything.

Also worth noting is that I only get this when doing a Debug compilation, never a Release. And that I (obviously) use a real device.

Erel · 2026-03-29T14:41:43+0100

Sandman said:
In my case this happens while the app is just idling and doing nothing. I have extensive logging available in the app so I'm certain it doesn't do anything.

Also worth noting is that I only get this when doing a Debug compilation, never a Release. And that I (obviously) use a real device.

If it only happens in debug mode when the app is idle then this is probably not a real issue. Network latency can cause such intermittent issues in debug mode.

Sandman · 2026-03-29T14:47:16+0100

Erel said:
If it only happens in debug mode when the app is idle then this is probably not a real issue.

That's actually been my feeling too, that it wasn't a real issue. But it is a bit annoying while coding.

Erel said:
Network latency can cause such intermittent issues in debug mode.

Would that be the latency between the app and the IDE? The communication used for the Debug compilation? Claude suggested that as an alternative so I started to consider if my Win machine was running too much crap, but it seemed fine. (I contemplated rebooting it, haven't tried yet.)

Android Question AppName not responding

LucasHeer

Active Member

LucasHeer

Active Member

Sagenut

Expert

LucasHeer

Active Member

LucasHeer

Active Member

Sagenut

Expert

LucasHeer

Active Member

LucasHeer

Active Member

PaulMeuris

Well-Known Member

Erel

B4X founder

Sandman

Expert

Erel

B4X founder

Sandman

Expert

Similar Threads

Android Question AppName not responding

Active Member

Active Member

Expert

Active Member

Active Member

Expert

Active Member

Active Member

Well-Known Member

B4X founder

Expert

B4X founder

Expert

Similar Threads

Privacy & Transparency

Privacy & Transparency