Missing logs while only service is running

[Ueland]

I noticed that while being at a location with bad cell coverage that AIMSICD kept complaining about chancing LAC, but that was never logged as long as the phone was in standby mode (black screen). Both the notification and in-app icon had changed to yellow so at least that part worked just fine, but upon opening the debugging view, i noticed that there was nothing there before the app starting.

While having the app open i did recieve log messages about changing LAC.

[E3V3A]

Please look manually in logcat via command line shell. The debug view was limited to 1000 items (lines) to preserve functionality. And 1000 lines in all log buffers get flashed by very quickly!

[He3556]

Is our Service running in background? I remember we talked about to keep the screen switched on. I found some things we can do to listen to the CellInfo all the time.

[E3V3A]

Yes, and it seem that the Service is not closing down after exiting the app, even when de-selected to do so in the settings. That is a bug, but I don't know if it's been fixed in the latest build.

[He3556]

I found some interesting information from @andr3jx in our Chat (Testroom) from December 2014, when we where talking about this. I am afraid we didn't discuss or solve it in the end:

You’ve mentioned that the screen needs to be on. Does the app not collect data when the screen is off? No, the app does not collect data when the screen is off on Android, except if you have experienced a dropped call. On some Android phones, there are bugs when trying to get signal data when the screen is off, so if we include this data it would skew the data.

There was an issue about that here - but i can find it (maybe it is closed for some reason?) @SecUpwN can you remember the issue?

@andr3jx conclusion was:

I think we are forced to keep screen on at minimum brightness to do monitoring in background

[SecUpwN]

Yes, I recall that we've talked about that, @He3556. If I recall correctly, what you're looking for is in #87 (comment) But I was not aware that our App currently doesn't do a thing when the screen is turned off! I mean, what are all the other similar projects do differently? What exactly do we have to do to fix it?

[He3556]

Well, our app is doing something when the screen is turned off - like the alert Ueland was talking about. But i would like to know what exactly is working. I need to check the logcat...
I wish there was some documentation about it :( But i will document it when i know...

[Ueland]

The app apparently work while in background, the only question is why it does not log as it should.

[E3V3A]

@Ueland I think by default, the baseband processor goes into a low energy state, kind of sleep, and only wakes when there is some events. So I guess only testing can reveal what is going on. I guess you can use ssh over wifi to look what happens when you turn off screen, or device goes to sleep.

[Ueland]

Hmm, god point! Perhaps SSH is the answer

[E3V3A]

I use SSHelper which works great. (With limited support info here.) Notice, that when screen is not on with SSHelper on top, the command line can be very laggy.

[SecUpwN]

@Ueland, would you please verify that this Issue still occurs with v0.1.25-alpha-b7?

[Ueland]

On my TODO. 👍

[Ueland]

Finally had an alert while the app was not open, looking good now. "I/AISMICD_DbAdaptor( 2184): CHANGING LAC!!! - Current LAC: 21201 Database LAC: 31201"

[SecUpwN]

@Ueland, you sound very happy about that - and I actually enjoy you do. Thanks! 😺