<?xml version="1.0" encoding="UTF-8"?><rss xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:atom="http://www.w3.org/2005/Atom" version="2.0"><channel><title><![CDATA[[Android client] Keepalive]]></title><description><![CDATA[<p dir="auto">Android client is losing connection to the server (even on wifi), and carries on as nothing happened. I think it should expect a keepalive packet from the server every [$configurable_interval] seconds and should it miss [$configurable_amount] packets, it should attempt reconnect. This might also possibly affect desktop client; happened to me at least once, but it's not as big a of a problem, since desktop connections tend to be more stable.</p>
]]></description><link>https://forum.netxms.org/topic/4377/android-client-keepalive</link><generator>RSS for Node</generator><lastBuildDate>Fri, 13 Nov 2026 08:37:19 GMT</lastBuildDate><atom:link href="https://forum.netxms.org/topic/4377.rss" rel="self" type="application/rss+xml"/><pubDate>Wed, 30 Mar 2016 00:51:36 GMT</pubDate><ttl>60</ttl><item><title><![CDATA[Reply to [Android client] Keepalive on Thu, 07 Jul 2016 12:01:01 GMT]]></title><description><![CDATA[<p dir="auto"><a class="plugin-mentions-user plugin-mentions-a" href="/user/ofca" aria-label="Profile: ofca">@<bdi>ofca</bdi></a> said in <a href="/post/20259">[Android client] Keepalive</a>:</p>
<blockquote>
<p dir="auto">I recently upgraded netxms and android client to 2.0.4 and unfortunately this is still unresolved. Client locks in some magic state, where not only it doesn't supply any notifications about alarms, but after bringing it to foreground and taping 'alarms' it keeps 'gathering data...' for few moments and then shows 'No items to show...'. Main menu shows 'Connected to server x.x.x.x'. Selecting reconnect fixes this.</p>
<p dir="auto">On a side note, alert filtering works flawlessly - thank you <img src="https://forum.netxms.org/assets/plugins/nodebb-plugin-emoji/emoji/android/1f642.png?v=72b86a538fc" class="not-responsive emoji emoji-android emoji--slightly_smiling_face" style="height:1.4em;width:auto;vertical-align:middle" title=":)" alt="🙂" /></p>
</blockquote>
<p dir="auto">Hi!,</p>
<p dir="auto">it is still unresolved (as per issue <a href="https://dev.raden.solutions/issues/1198" rel="nofollow ugc">https://dev.raden.solutions/issues/1198</a> not yet closed) because I did not find time to investigate, I'm sorry  <img src="https://forum.netxms.org/assets/plugins/nodebb-plugin-emoji/emoji/android/1f61e.png?v=72b86a538fc" class="not-responsive emoji emoji-android emoji--disappointed" style="height:1.4em;width:auto;vertical-align:middle" title=":(" alt="😞" /></p>
<p dir="auto">Regards,<br />
Marco</p>
]]></description><link>https://forum.netxms.org/post/20372</link><guid isPermaLink="true">https://forum.netxms.org/post/20372</guid><dc:creator><![CDATA[Jmp_3f8h]]></dc:creator><pubDate>Thu, 07 Jul 2016 12:01:01 GMT</pubDate></item><item><title><![CDATA[Reply to [Android client] Keepalive on Mon, 27 Jun 2016 08:34:10 GMT]]></title><description><![CDATA[<p dir="auto">I recently upgraded netxms and android client to 2.0.4 and unfortunately this is still unresolved. Client locks in some magic state, where not only it doesn't supply any notifications about alarms, but after bringing it to foreground and taping 'alarms' it keeps 'gathering data...' for few moments and then shows 'No items to show...'. Main menu shows 'Connected to server x.x.x.x'. Selecting reconnect fixes this.</p>
<p dir="auto">On a side note, alert filtering works flawlessly - thank you <img src="https://forum.netxms.org/assets/plugins/nodebb-plugin-emoji/emoji/android/1f642.png?v=72b86a538fc" class="not-responsive emoji emoji-android emoji--slightly_smiling_face" style="height:1.4em;width:auto;vertical-align:middle" title=":)" alt="🙂" /></p>
]]></description><link>https://forum.netxms.org/post/20259</link><guid isPermaLink="true">https://forum.netxms.org/post/20259</guid><dc:creator><![CDATA[ofca]]></dc:creator><pubDate>Mon, 27 Jun 2016 08:34:10 GMT</pubDate></item><item><title><![CDATA[Reply to [Android client] Keepalive on Tue, 05 Apr 2016 12:57:37 GMT]]></title><description><![CDATA[<p dir="auto"><a class="plugin-mentions-user plugin-mentions-a" href="/user/ofca" aria-label="Profile: ofca">@<bdi>ofca</bdi></a> said in <a href="/post/19563">[Android client] Keepalive</a>:</p>
<blockquote>
<p dir="auto">Actually it isn't the culprit. Or at least is one of many: same thing happens overnight on my home wifi, and there were no outages.</p>
</blockquote>
<p dir="auto">Thank you for adding info, the problem needs a deeper investigation. I'll post news when available.</p>
<p dir="auto">Regards,<br />
Marco</p>
]]></description><link>https://forum.netxms.org/post/19564</link><guid isPermaLink="true">https://forum.netxms.org/post/19564</guid><dc:creator><![CDATA[Jmp_3f8h]]></dc:creator><pubDate>Tue, 05 Apr 2016 12:57:37 GMT</pubDate></item><item><title><![CDATA[Reply to [Android client] Keepalive on Tue, 05 Apr 2016 12:19:55 GMT]]></title><description><![CDATA[<p dir="auto">Actually it isn't the culprit. Or at least is one of many: same thing happens overnight on my home wifi, and there were no outages.</p>
]]></description><link>https://forum.netxms.org/post/19563</link><guid isPermaLink="true">https://forum.netxms.org/post/19563</guid><dc:creator><![CDATA[ofca]]></dc:creator><pubDate>Tue, 05 Apr 2016 12:19:55 GMT</pubDate></item><item><title><![CDATA[Reply to [Android client] Keepalive on Mon, 04 Apr 2016 19:06:20 GMT]]></title><description><![CDATA[<p dir="auto"><a class="plugin-mentions-user plugin-mentions-a" href="/user/ofca" aria-label="Profile: ofca">@<bdi>ofca</bdi></a> said in <a href="/post/19522">[Android client] Keepalive</a>:</p>
<blockquote>
<p dir="auto">Sending keepalives and reacting to lack of them should be bulletproof.</p>
</blockquote>
<p dir="auto">In theory, receiving properly the connection notification from Android should have the same result. I have the impression that the poor coverage can be the culprit: in that case I guess that the app isn't able to properly handshake with the server going in timeout without retrying properly... I'll try to investigate.</p>
<p dir="auto">I've opened an issue:</p>
<p dir="auto"><a href="https://dev.raden.solutions/issues/1198" rel="nofollow ugc">https://dev.raden.solutions/issues/1198</a></p>
<p dir="auto">Regards,<br />
Marco</p>
]]></description><link>https://forum.netxms.org/post/19559</link><guid isPermaLink="true">https://forum.netxms.org/post/19559</guid><dc:creator><![CDATA[Jmp_3f8h]]></dc:creator><pubDate>Mon, 04 Apr 2016 19:06:20 GMT</pubDate></item><item><title><![CDATA[Reply to [Android client] Keepalive on Thu, 31 Mar 2016 04:34:49 GMT]]></title><description><![CDATA[<p dir="auto">No pattern, except maybe for moving through some poor-coverage areas. It just reliably becomes quiet after some time, no alerts, no nothing -- only reconnect helps. And it's not only my problem -- it happens on totally different phone with stock os too. Sending keepalives and reacting to lack of them should be bulletproof.</p>
]]></description><link>https://forum.netxms.org/post/19522</link><guid isPermaLink="true">https://forum.netxms.org/post/19522</guid><dc:creator><![CDATA[ofca]]></dc:creator><pubDate>Thu, 31 Mar 2016 04:34:49 GMT</pubDate></item><item><title><![CDATA[Reply to [Android client] Keepalive on Wed, 30 Mar 2016 17:26:54 GMT]]></title><description><![CDATA[<p dir="auto"><a class="plugin-mentions-user plugin-mentions-a" href="/user/ofca" aria-label="Profile: ofca">@<bdi>ofca</bdi></a> said in <a href="/post/19496">[Android client] Keepalive</a>:</p>
<blockquote>
<p dir="auto">Android client is losing connection to the server (even on wifi), and carries on as nothing happened. I think it should expect a keepalive packet from the server every [$configurable_interval] seconds and should it miss [$configurable_amount] packets, it should attempt reconnect. This might also possibly affect desktop client; happened to me at least once, but it's not as big a of a problem, since desktop connections tend to be more stable.</p>
</blockquote>
<p dir="auto">Android client receives broadcast notification from OS, so when the connection drops or is re-established the app should disconnect and reconnect according to that behaviour (unless something is changed in recent versions of OS) .<br />
Did you notice a specific situation when this doesn't happens?</p>
<p dir="auto">Best regards,<br />
Marco.</p>
]]></description><link>https://forum.netxms.org/post/19515</link><guid isPermaLink="true">https://forum.netxms.org/post/19515</guid><dc:creator><![CDATA[Jmp_3f8h]]></dc:creator><pubDate>Wed, 30 Mar 2016 17:26:54 GMT</pubDate></item></channel></rss>