<?xml version="1.0" encoding="UTF-8" ?>
<?xml-stylesheet type="text/xsl" href="https://devzone.nordicsemi.com/cfs-file/__key/system/syndication/rss.xsl" media="screen"?><rss version="2.0" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:slash="http://purl.org/rss/1.0/modules/slash/" xmlns:wfw="http://wellformedweb.org/CommentAPI/" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Notification packet loss iOS/Android</title><link>https://devzone.nordicsemi.com/f/nordic-q-a/64950/notification-packet-loss-ios-android</link><description>From my understanding, notifications have guaranteed in-order delivery at the lower levels. I&amp;#39;m working on a small file transfer system out of an nrf52840, trying to decide if I can design the protocol for a lossless system. 
 Is it possible for the BLE</description><dc:language>en-US</dc:language><generator>Telligent Community 13</generator><lastBuildDate>Wed, 19 Aug 2020 12:53:23 GMT</lastBuildDate><atom:link rel="self" type="application/rss+xml" href="https://devzone.nordicsemi.com/f/nordic-q-a/64950/notification-packet-loss-ios-android" /><item><title>RE: Notification packet loss iOS/Android</title><link>https://devzone.nordicsemi.com/thread/265328?ContentTypeID=1</link><pubDate>Wed, 19 Aug 2020 12:53:23 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:ef3c1b0a-bd12-4711-9cac-7436d68cb309</guid><dc:creator>Aleksander Nowakowski</dc:creator><description>&lt;p&gt;Hello,&lt;/p&gt;
&lt;p&gt;So far we didn&amp;#39;t have problems with this. On Android, the value of a characteristic is a shared resource for writing and reading/notifications, so make sure you don&amp;#39;t reuse the same characteristic for writing and getting values. Otherwise you may receive what you have just send. Also, try to avoid setting another handler in connectGatt. All notifications will be received on the BLE handler without another delay/copying to your thread. On iOS there seem to be no issues.&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item></channel></rss>