Android Question Debugging of hardware (?) problem

[rboeck]

Hi,

i made an app, which i can use on several devices; on one device i have the problem of permanent Activity_Resume's of my app; network connections are dropped and my app is in an ongoing refresh und new start. Yesterday i made a clean install, but the problem is still here.
I have tried to read the unfiltred log files and found strange lines:

Dock state change from 0 to 1 and reverse

Anyone with an idea, how to find out more?

 

[Erel]

Is the activity paused before it is resumed?

 

[rboeck]

I think no: a have a log statement in pause, but i never i see anything in the log file. I see the log from Activity_Resume every three seconds and Activity_Create is following. I have an mqtt client running and i get

** Activity (adressliste) Resume **
Activity_Resume:
** Activity (adressliste) Pause, UserClosed = false **
Activity_Pause:false
Reposting event: mqtt_connected
Reposting event: mqtt_connected
Reposting event: mqtt_disconnected
Reposting event: mqtt_disconnected
** Activity (adressliste) Create, isFirst = false **

Maybe my battery pack is not in best condition, but i can work for three hours. But i the battery pack gets fully loaded, i see a connect / disconnect effect also.

 

[Erel]

The first step is to create a new empty project and run it on the device. Do you see any strange behavior?

 

[rboeck]

I used a neutral project TabHostExtrasDemo and i get the same effect, here from the log file:

Spoiler: Log file:

** Activity (main) Pause, UserClosed = false **
Actity Pause
** Activity (main) Create, isFirst = false **
The current TabIndicator TextSize is: 21 pixels
The new TabIndicator TextSize is: 30 pixels
** Activity (main) Resume **
Activity Resume
** Activity (main) Pause, UserClosed = false **

I think, the problem is device / hardware specific... I have another tablet, only one generation older and i dont see the effect here. If i disconnect, the screen stops blinking, it seems that the usb cable (or loading= is maybe part of the problem.

 

[Erel]

It does look like a device specific issue. You can use B4A-Bridge if you think that the USB is the problem.