Android Question AppName not responding

LucasHeer · Mar 28, 2026

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 · Mar 28, 2026

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 · Mar 28, 2026

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

LucasHeer · Mar 28, 2026

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 · Mar 28, 2026

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 · Mar 28, 2026

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 · Mar 28, 2026

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 · Mar 29, 2026

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 · Mar 29, 2026

It is probably device related...

Erel · Mar 29, 2026

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 · Mar 29, 2026

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 · Mar 29, 2026

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 · Mar 29, 2026

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.)

LucasHeer · Mar 29, 2026

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

My unfiltered logs reported the same as @Sandman

B4X:

Reason: executing service com.testapp.app/.starter, waited 52119ms
ANR in b4a.example ... Reason: executing service b4a.example/.starter, waited 20002ms

^^ With an empty starter

However, it seems that Google may have put out an overnight update fixing this issue @Sandman Do you see the same resolution?

I also use https://github.com/genymobile/scrcpy to show my phone screen over zoom calls, and I had noticed it was laggy beyond usability. It seems that maybe Google had put out a bad update during this time.

Thank you again sir!

Erel · Mar 30, 2026

Sandman said:
Would that be the latency between the app and the IDE?

It might be.

Sandman · Mar 30, 2026

LucasHeer said:
I also use https://github.com/genymobile/scrcpy to show my phone screen over zoom calls, and I had noticed it was laggy beyond usability.

I also use scrcpy, so even if that had worked great for the longest time it became a suspect. So I tested now to not use it, and that actually made a positive change. (I also tried updating scrcpy from 3.3.3 to 3.3.4 which didn't seem to help at all.) I do still get the "AppName isn't responding" message even when not using scrcpy, but it takes way longer for it to appear.

LucasHeer said:
However, it seems that Google may have put out an overnight update fixing this issue @Sandman Do you see the same resolution?

I checked, and I see no update of any kind. Was this something you read about or actually got installed? What's the version number for you?

However I did update to Android 16 somewhat recently, and I wonder if that created a bottleneck somewhere, which is made worse by the streaming of scrcpy... I'll put out a post to check how things are working for other people with Pixel and Android 16.

Post to check if there's more of us with this combination:

Got a Pixel phone + usb connection + Android 16?

There's two of us with that combination here in the forum that started getting "AppName isn't responding" messages. If you are have the combination above, could you please comment on whether you get these messages now and then? (Also post if you have the combination and do not get the...

www.b4x.com

LucasHeer · Mar 30, 2026

Sandman said:
I also use scrcpy, so even if that had worked great for the longest time it became a suspect. So I tested now to not use it, and that actually made a positive change. (I also tried updating scrcpy from 3.3.3 to 3.3.4 which didn't seem to help at all.) I do still get the "AppName isn't responding" message even when not using scrcpy, but it takes way longer for it to appear.

I checked, and I see no update of any kind. Was this something you read about or actually got installed? What's the version number for you?

However I did update to Android 16 somewhat recently, and I wonder if that created a bottleneck somewhere, which is made worse by the streaming of scrcpy... I'll put out a post to check how things are working for other people with Pixel and Android 16.

Scrcpy was amazing! It worked great for the longest time, and then recently.. Like overnight, this "App not responding" issue started.

I am running Android 17 beta on my pixel 9 pro. I still see the message every few hours. Not near as bad as before.

I have a pixel 7 pro on android 14, I will test as-is and then upgrade to android 16 and test for you

LucasHeer · Mar 30, 2026

Sandman said:
I also use scrcpy, so even if that had worked great for the longest time it became a suspect. So I tested now to not use it, and that actually made a positive change. (I also tried updating scrcpy from 3.3.3 to 3.3.4 which didn't seem to help at all.) I do still get the "AppName isn't responding" message even when not using scrcpy, but it takes way longer for it to appear.

I checked, and I see no update of any kind. Was this something you read about or actually got installed? What's the version number for you?

However I did update to Android 16 somewhat recently, and I wonder if that created a bottleneck somewhere, which is made worse by the streaming of scrcpy... I'll put out a post to check how things are working for other people with Pixel and Android 16.

Post to check if there's more of us with this combination:

Got a Pixel phone + usb connection + Android 16?

There's two of us with that combination here in the forum that started getting "AppName isn't responding" messages. If you are have the combination above, could you please comment on whether you get these messages now and then? (Also post if you have the combination and do not get the...

www.b4x.com

No problem with android 14 on P7P, after upgrade i let it sit for 3-4 minutes and got "App not responding". Scrcpy slow as well

Sandman · Mar 30, 2026

LucasHeer said:
No problem with android 14 on P7P, after upgrade i let it sit for 3-4 minutes and got "App not responding". Scrcpy slow as well

Thanks for checking that, I appreciate it.

Ok, so we'll just assume it's an Android 16 issue for the time being. And now I asked Claude about this combo:

When I updated my Pixel phone to Android 16 I started getting more "App isn't responding" messages. Is this a known thing?

Yes, this is definitely a known issue — you're not imagining it. Here's a summary of what's been going on:

Full response here:

https://claude.ai/share/0023e258-95e4-4b53-aaab-4672d818c489

LucasHeer · Mar 30, 2026

Sandman said:
Thanks for checking that, I appreciate it.

Ok, so we'll just assume it's an Android 16 issue for the time being. And now I asked Claude about this combo:

When I updated my Pixel phone to Android 16 I started getting more "App isn't responding" messages. Is this a known thing?

Yes, this is definitely a known issue — you're not imagining it. Here's a summary of what's been going on:

Full response here:

https://claude.ai/share/0023e258-95e4-4b53-aaab-4672d818c489

Absolutely! And very interesting!

I am not sure what they changed, but overnight my experience with this got a ton better with P9P Android 17 beta.

Before though, it happened to me nonstop with USB+WiFi debugging, and debug/release builds even with empty B4A.Example app.

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

Active Member

B4X founder

Expert

Active Member

Active Member

Expert

Active Member

Similar Threads

Privacy & Transparency

Privacy & Transparency