@lakwnikos If you get pop up telling that a crash occurred, please proceed with sending me a crash report. In your case now, if restart doesn't help, you will have to reinstall AndStatus.
AndStatus v.27.01 published at Beta testing channel. Fixed compatibility problem with Android N (workaround found) - this is a bug in Android N actually: I raised a ticket on this: https://code.google.com/p/android/issues/detail?id=215525
@mmn I found a bug in GNU Social Twitter API, which causes unnecessary network traffic and delays: it ignores "since_id" parameter in a "search" request. As a result every subsequent search request returns the same list of ”notices". See e.g. https://loadaverage.org/api/search.json?count=200&q=andstatus&since_id=8226489 Please fix this. Upcoming changes to AndStatus will allow users to use Search very conveniently, including automatic syncing of "Search timelines", and this server-side bug can cause unnecessary load... BTW, Twitter reacts properly and in a case no newer tweets exist it returns JSON file with metadata of 352 bytes ;-)
@andstatus@loadaverage.org I have automatic sync frequency set to once in an hour, so you can see a screenshot taken two hours later, after the third automatic sync: No more messages were downloaded during subsequent syncs meaning that network traffic for syncs was minimal. At the screenshot you can also see that network error occurred for one timeline and error message was logged. https://loadaverage.org/attachment/3116472
@andstatus@loadaverage.org In order to give Users more information on efficiency of syncing I added another column to the timeline list: "Dnl." - it shows total number of messages downloaded vs new messages, shown in the next column. So e.g. you can see at the attached screenshot that "Sent for yvolk/Twitter" timeline was synced once (1}, downloaded 192 messages (after this application upgrade no sync history existed for this timeline, so it downloaded maximum number configured), but only 1 of those messages appeared to be new, i.e. only one message was not stored in the local cache yet. https://loadaverage.org/attachment/3116442
@sierpeverde @desidia @spectrumgirl @fanta usando el móvil con datos (vamos, sin wifi), se nota muchísimo un menor consumo si se usa un cliente como #AndStatus o #Twidere. Para mí esa es la mejor razón para usarlos antes que el cliente web del nodo
@vinzv @nobse BTW AndStatus now has the option: "Syncing->Don't synchronize old messages...". It may speed up syncing in a case you use only manual synchronization. @benediktg