Android Question app DOES NOT RESPOND dialogue

[peacemaker]

I have found that recent months my apps (mostly using HttpUtils2) after start in several seconds are followed by the "app does not respond" system dialog.
In long FOR loops i always use the code like

If (i mod 100) = 0 then DoEvents

B4A is always latest actual (now v.4.3), but test devices are the same recent years (see my signature).

But now in app template with the service working with the accelerometer, without loops and DoEvents it has occured also :-(

Erel, full source code is emailed to you.
Any help ?

Team, did you have such issue recent 2-3 years (at least with apps using HttpUtils2) ?

 

[DonManfred]

Using DoEvents is not a solution.
The solution will be using Threads and/or Async tasks for longer loops. Maybe a service.

 

[peacemaker]

This time the service has only

Sub Service_Create
others.Notif("Started OK.", False, False, Main, "")
Service.StartForeground(8, Notif1)

Try
    sensor.Initialize(sensor.TYPE_ACCELEROMETER)
    AccelExists = True
Catch
    AccelExists = False
    ToastMessageShow("No accel: stopped", True)
    CallSub(Main, "Activity_Close")
    StopService(Me)
End Try
End Sub

Private Sub Sensor_SensorChanged (Values() As Float)
SensorX1 = Round(Values(0)) * 10
SensorY1 = Round(Values(1)) * 10
SensorZ1 = Round(Values(2)) * 10
End Sub

sensor.StartListening("Sensor") is used separately, by an interface button

 

[Erel]

The first step is to remove all the DoEvents calls. They will only cause problems.

HttpUtils2 doesn't block the main thread and will not cause such an error.

You need to find out which part of the code blocks the main thread.

 

[peacemaker]

Clear, but this app with accelerometer without HttpUtils2 ? (i emailed the full source)

 

[Erel]

Try to reproduce it in a small project and upload the project.

 

[peacemaker]

Indeed - DoEvents was the issue...
Solved.
Do not use DoEvents at service start.

But how to be sure correctly that a service is started, all initialized, database is opened.... before letting the user to work with the activity ?
In big app it's needed long time for whole initializations.

 

[Erel]

Are you starting the service when the activity is created? You can use CallSubDelayed to call a sub in the activity from the service when everything is ready.

 

[peacemaker]

Yes, from activity, but activity interface depends on the service work, that should be inited first, for rather long time.
Thanks for suggestion.