JavaJens
JavaJens
You can try to get a debug log. There shouldn't be any artificial delay. Iirc there might be an exponential backoff if there are connection problems.
There is no log in there :wink: I don't know if there is sth. special about Jolla. Maybe try adb?
adb http://developer.android.com/tools/help/adb.html The most likely assumption that I can make is that some power savings mode kicks in. Could that be the case?
Usually the log from the menu should suffice, maybe just try again?
@mjtorn yes, I mean the gist. Usually this contains all debug information you get through adb without the hassle. If this doesn't work, I fear adb is the only way.
@mjtorn there is heavy logging in the app, but I'm afraid this is a limitation of Jolla.
@mjtorn The regular client uses websockets while the app is open. This is used to prevent the delay introduced by GCM. But as battery usage increases with websockets, the socket...
As the official android Application supports this, I would assume so. I guess some traffic snooping would help here...
Upvote on batch-summit as well. Now I have to visit each cache in history, wait for the login page to be loaded and then click log. Or is there another...
Thanks, didn't knew about this feature.