Android Question Got a Pixel phone + usb connection + Android 16?

[Sandman]

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

If you want to read more about this issue, here is the thread:
www.b4x.com/android/forum/threads/appname-not-responding.170706/

 

[xeriko]

Same here — I have that combination and I'm getting the "AppName isn't responding" messages too. And it's not just now and then for me; it pops up roughly every 20 seconds, which makes it really annoying to work with.

 

[Alessandro71]

Maybe not related at all, but I’m receiving complaints from users with Bluetooth issues on pixel phones after the latest Google patch.
maybe that latest patch has stability problems

 

[Dave O]

I just got a crash reported by a user using my app on their Pixel 3a (Android 12), which was working fine until a few days ago. She just got a new Pixel 9a (Android 16) and the same crash is happening to it - <appname> keeps stopping - on app startup.

Wonder if mine is related to yours?

 

[Jmu5667]

I have a Pixel 6a/Android 16 with all our apps running and have never encountered this issue. Has anyone done a 'adb logcat -d > device.txt' ? I would be glad to help if you want to send me an apk.

John.

 

[Sandman]

Wonder if mine is related to yours?

Best guess: yes.

Has anyone done a 'adb logcat -d > device.txt' ?

Oh yes, quite a bit. The only thing ever that comes up is that there is something with the Starter, even though it's completely unmodified from a blank project. (I'm guessing that there is a minor possibility that we'll get a B4A update at some point, with updated behind-the-scenes code for the Starter.) Check out the linked thread in #1 for a bit more info.

 

[Alex_197]

Best guess: yes.


Oh yes, quite a bit. The only thing ever that comes up is that there is something with the Starter, even though it's completely unmodified from a blank project. (I'm guessing that there is a minor possibility that we'll get a B4A update at some point, with updated behind-the-scenes code for the Starter.) Check out the linked thread in #1 for a bit more info.

Guys, I'm might be mistaken correct me if I wrong, but as far as I remember there are some settings that turn on / off 16 KB mode on Google Pixel phone.

Checked with Google


Key Details on 16KB Settings

• Purpose: To enable 16KB memory page size instead of the standard 4KB, reducing RAM overhead and improving app performance.
• Requirement: Your Pixel 9a must be running Android 15 QPR2 or later.
• Enabling the Setting:
  1. Go to Settings > System > Developer options.
  2. Locate and toggle Boot with 16 KB page size.
• Crucial Note: Enabling this setting requires an unlocked bootloader and will trigger a factory reset to reformat the device's file system.
• Reverting: Switching back to 4KB also requires a factory reset.
  
  
  Android Open Source Project +5

This setting is primarily for developers to test 16KB compatibility before it becomes mandatory for app submissions to the Play Store.

 

[Sandman]

What makes you think that is relevant?

 

[Erel]

It looks like a debugger issue. The exact cause isn't yet clear, however removing the Starter service seems to solve it. At least here...

Please try it. If using B4XPages then the starter service is not too useful anyway.

 

[Dave O]

If it's a debugger issue, then does that mean that it only happens in Debug mode? (My reported crashes are in a production app (Release Obfuscated mode).)

 

[Erel]

True. However without more information it is difficult to say whether this is actually the same issue. If this is a B4XPages project then worth testing without the starer service.

 

[Erel]

Still investigating. It is related to the starter service failing to start properly.

You can see it by adding a log message in Service_Start. It doesn't get called in debug mode. Seems to work fine in release mode. Try and report if you encountered something different.

 

[Erel]

Whoever encountered this error, please try it with this code in the starter service:

Sub Service_Create
    Log("Service_Create")
    StopService(Me)
End Sub

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

Based on my tests it solves the issue related to the service execute ANR.

 

[Sandman]

Whoever encountered this error, please try it with this code in the starter service

That would be me. I'll check it Monday at the latest and report back.

 

[Sandman]

Based on my tests it solves the issue related to the service execute ANR

I have tried now, and it does indeed solve the issue. Thank you, it's good to be able to code using Debug again.

The only thing I use Starter for nowadays is the Application_Error sub, the StopService(Me) doesn't in any way interfere with that, right?

Just because I'm curious, does this mean that we will get an updated B4A with updated behind-the-scenes code for Starter at some point, so we don't have to have to stop the service? Or will the Starter template code get an update to contain the StopService(Me)?

 

[Alessandro71]

Is this limited to Android 16 on Pixel phones?
because I have Android 16 users with no issues so far.

 

[Dave O]

My starter crash on a user's Pixel 3a is for a release-obfuscated app (not debug) and NOT running B4XPages.

So still not sure if my crash is related to this one, but here's the details just in case they're useful to y'all:

Exception java.lang.RuntimeException:
  at android.app.ActivityThread.handleCreateService (ActivityThread.java:4567)
  at android.app.ActivityThread.access$1700 (ActivityThread.java:256)
  at android.app.ActivityThread$H.handleMessage (ActivityThread.java:2110)
  at android.os.Handler.dispatchMessage (Handler.java:106)
  at android.os.Looper.loopOnce (Looper.java:201)
  at android.os.Looper.loop (Looper.java:288)
  at android.app.ActivityThread.main (ActivityThread.java:7870)
  at java.lang.reflect.Method.invoke
  at com.android.internal.os.RuntimeInit$MethodAndArgsCaller.run (RuntimeInit.java:548)
  at com.android.internal.os.ZygoteInit.main (ZygoteInit.java:1003)
Caused by java.lang.RuntimeException:
  at anywheresoftware.b4a.BA.raiseEvent2 (BA.java:258)
  at anywheresoftware.b4a.BA.raiseEvent (BA.java:201)
  at name.obrien.dave.lister.starter.onCreate (starter.java:56)
  at android.app.ActivityThread.handleCreateService (ActivityThread.java:4554)